From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] fakeroot: update to upstream version 1.18.4
Date: Sat, 1 Dec 2012 23:08:33 -0600 [thread overview]
Message-ID: <50BAE251.9050702@windriver.com> (raw)
In-Reply-To: <CAF6bG8fwWSuemoc1kKJVHKUt8KJ5F4WR_WskTyoPJw26C3Qf+w@mail.gmail.com>
On 12/1/12 4:12 PM, Marko Lindqvist wrote:
> On 1 December 2012 14:14, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>> On Saturday 01 December 2012 11:38:37 Marko Lindqvist wrote:
>>> License is now GPLv3
>>>
>>> Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
>>> ---
>>
>> Just out of interest, are you (or is anyone else for that matter) using
>> fakeroot in preference to pseudo which we already build as part of the normal
>> build process?
>
> I'm not at the moment. Later I may bring to OpenEmbedded environment
> some scripts that use fakeroot, but even then adjusting the scripts is
> an option.
If there is anything that fakeroot is capable of doing that pseudo does not, or
another reason why you want to use fakeroot instead, please let us know.
pseudo was developed originally to deal with a number of stability, enhancement
and other requirements after using fakeroot, fakechroot and related tooling.
(Note, if you are using RPM, fakechroot likely won't work because it doesn't
support going in and out of chroot across processes.)
>
> - ML
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2012-12-02 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 9:38 [PATCH] fakeroot: update to upstream version 1.18.4 Marko Lindqvist
2012-12-01 12:14 ` Paul Eggleton
2012-12-01 22:12 ` Marko Lindqvist
2012-12-02 5:08 ` Mark Hatle [this message]
2012-12-05 15:11 ` Martin Jansa
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=50BAE251.9050702@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.