public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Alf Høgemark" <alf@i100.no>
To: development@lists.ipfire.org
Subject: Why must the "make.sh" be run as root ?
Date: Sun, 02 Mar 2014 10:56:58 +0100	[thread overview]
Message-ID: <5313006A.3050908@i100.no> (raw)

[-- 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


             reply	other threads:[~2014-03-02  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02  9:56 Alf Høgemark [this message]
2014-03-03  8:24 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5313006A.3050908@i100.no \
    --to=alf@i100.no \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox