Salix Forums

Hello,

Please pardon me if this question sounds very silly.

I have a basic doubt. To create packages, I need to use the command makepkg which is not available when I have logged in as a non-root user. So, should I always login as root while creating packages or is there any other way to do it?

Thanks for your help.

Anand

I recommend you use fakeroot, like this: so you can also have a build log. In that case, you should specify makepkg with a full path in the Slackbuild: Using fakeroot has the huge advantage that if something tries to install in you system instead of the packaging directory, you'll get an error and there is no chance that it will slip out.

Or event better :
(OLDPATH=$PATH; PATH=/sbin:/usr/sbin/:$PATH; fakeroot name.Slackbuild 2>&1 | tee build-name.log; PATH=$OLDPATH; unset OLDPATH)

gapan wrote:I recommend you use fakeroot, like this:

Code: Select all

fakeroot name.Slackbuild 2>&1 | tee build-name.log

so you can also have a build log. In that case, you should specify makepkg with a full path in the Slackbuild:

Code: Select all

/sbin/makepkg -l y -c n ...

Using fakeroot has the huge advantage that if something tries to install in you system instead of the packaging directory, you'll get an error and there is no chance that it will slip out.

Sorry for picking up this ancient thread, but I'd like to know - is this still the recommended way building packages (apart from using sourcery)?

Yes.

I have tried to build a newer git using Pat's slackBuild from here, but when I run it as recommended: I get the following error: What am I doing wrong?
Note that I have also used also JRD's suggestion from this thread, but got the same error.

It is:

Isn't the current dir in your $PATH?

Try:

It isn't on the $PATH, but adding "./" as you suggested brought up the same error message.