Why must the "make.sh" be run as root ?

Why must the "make.sh" be run as root ?

[Alf Høgemark]

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

Hi

I'm trying to do a full build of ipfire, following instructions on :
http://wiki.ipfire.org/en/development/build

I have been able to do a full build (except for build of cdrom failing, 
it seems to be tar complaining that usb/bin/ntpd and other ntp files are 
missing),
but I am wondering why I need to run the make.sh as root.

I can see in the make.sh that a symlink is made for "/tools", so I guess 
one needs root for that.
Is that the only reason ?
Or is the build process putting files on my computer outside the folder 
where I have the source code repo from git ?

Could one use the "fakeroot" command instead, if needed ?

I do not like runing build commands as root, being afraid that something 
is installed / changed somewhere on my development machine.
So it would mean that I need a separate virtual build machine for 
building ipfire.


Regards
Alf

Re: Why must the "make.sh" be run as root ?

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

Morning,

On Sun, 2014-03-02 at 10:56 +0100, Alf Høgemark wrote:
> Hi
> 
> I'm trying to do a full build of ipfire, following instructions on :
> http://wiki.ipfire.org/en/development/build
> 
> I have been able to do a full build (except for build of cdrom failing, 
> it seems to be tar complaining that usb/bin/ntpd and other ntp files are 
> missing),
> but I am wondering why I need to run the make.sh as root.

To fix the ntp issue, just pull again and rebuild.

make.sh must be run as root.

> I can see in the make.sh that a symlink is made for "/tools", so I guess 
> one needs root for that.
> Is that the only reason ?
> Or is the build process putting files on my computer outside the folder 
> where I have the source code repo from git ?

The /tools symlink is the only thing that is created outside the build/
directory.
The other reason why we need root permissions is to create files inside
the build chroot tree as root.

> Could one use the "fakeroot" command instead, if needed ?

Yes, fakeroot could be used instead of actual root permissions, but we
don't use it.

> I do not like runing build commands as root, being afraid that something 
> is installed / changed somewhere on my development machine.
> So it would mean that I need a separate virtual build machine for 
> building ipfire.

Indeed, having an extra machine for this purpose does not hurt because
virtualization provides a good container that isolates the build system
from the host system.

-Michael

> 
> 
> Regards
> Alf
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development