From: Kyle Moffett <mrmacman_g4@mac.com>
To: Ryan Anderson <ryan@michonline.com>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: git-diff-files and fakeroot
Date: Tue, 17 Jan 2006 00:59:24 -0500 [thread overview]
Message-ID: <95E085A7-B910-4C01-BA6E-43971A6F5F97@mac.com> (raw)
In-Reply-To: <20060117052758.GA22839@mythryan2.michonline.com>
On Jan 17, 2006, at 00:27, Ryan Anderson wrote:
> On Mon, Jan 16, 2006 at 06:36:39PM -0800, Junio C Hamano wrote:
>> BTW, Ryan, I suspect this is where you try to append "-dirty" to
>> the version number. But I wonder why you are doing the build
>> under fakeroot to begin with? Wasn't the SOP "build as
>> yourself, install as root"?
>
> That's exactly what started this search, because I was running
> "make deb-pkg". (Effectively.) dpkg-buildpackage wants to think it
> is running as root, either via sudo or via fakeroot. I had my
> build environment switched over entirely to fakeroot, as it just
> seems to be a better practice, but I've temporarily switched back
> to sudo.
>
> However, your explanation has pointed out to me how I can solve
> this - run "fakeroot -u" instead of "fakeroot", and I think it will
> be fixed.
You should run "make" first, then after that completes run "fakeroot
make deb-pkg". I think this is similar to what the Debian package
"kernel-package" does, except it substitutes an alternate "debian/"
directory. IIRC, it just runs "make install" as a normal user to a
staging directory, then runs "$(ROOTCMD) dpkg-deb -b [...]" to build
the package. IMHO it's somewhat of a cleaner solution, and I've used
it for several years now with no issues.
Cheers,
Kyle Moffett
--
I have yet to see any problem, however complicated, which, when you
looked at it in the right way, did not become still more complicated.
-- Poul Anderson
next prev parent reply other threads:[~2006-01-17 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43CC5231.3090005@michonline.com>
[not found] ` <7vzmlvk2bs.fsf@assigned-by-dhcp.cox.net>
2006-01-17 5:27 ` Ryan Anderson
2006-01-17 5:59 ` Kyle Moffett [this message]
2006-01-17 6:08 ` Ryan Anderson
2006-01-17 18:10 ` Sam Ravnborg
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=95E085A7-B910-4C01-BA6E-43971A6F5F97@mac.com \
--to=mrmacman_g4@mac.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@michonline.com \
/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
all inboxes | Powered by JetHome®