On Mon, Mar 31, 2008 at 5:12 PM, Bryan Kadzban
<[EMAIL PROTECTED]> wrote:
> But any kind of DESTDIR type
> setup would require it, if the package's "make install" is run as a
> non-root user.
fakeroot is not an absolute requirement for install-root style PM. I
use the following wrappers to avoi
On undefined, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> But what is being described here is much more than just a DESTDIR
> installation method. To me, this sounds like pure PM, and probably
> more than LFS should take on.
>
It is not more than the DESTDIR method. If packages are installed
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
taipan wrote:
> It still has me wondering if this proposed branch would require or
> benefit from the inclusion of the 'fakeroot' package, as used by
> diy-linux? I've never built either, & am uncertain of it's precise
> function - so this is p
Sukucorp Sukucorp wrote these words on 03/31/08 16:40 CST:
> On undefined, Dave Wheeler <[EMAIL PROTECTED]> wrote:
>> I agree w/ pretty much everything said below and would also like to
>> see a DESTDIR-branch. I'd add the uninstall commands should also be
>> broken out into pre- and post- stage
On undefined, Dave Wheeler <[EMAIL PROTECTED]> wrote:
> I agree w/ pretty much everything said below and would also like to
> see a DESTDIR-branch. I'd add the uninstall commands should also be
> broken out into pre- and post- stages. An example would be calling
> pwunconv and grpunconv if you
I agree w/ pretty much everything said below and would also like to
see a DESTDIR-branch. I'd add the uninstall commands should also be
broken out into pre- and post- stages. An example would be calling
pwunconv and grpunconv if you uninstall shadow - they need to be
executed before removing the
Randy McMurchy wrote:
>
> Thoughts from others?
>
And there's me thinking you were just playing with your chopper...
That sounds great - I'd be really interested in seeing some of the meat.
It seemed that the great enthusiasm we had here a few weeks ago for a
LFS-ng had died almost as fast a
On Mon, Mar 31, 2008 at 9:53 AM, Randy McMurchy
<[EMAIL PROTECTED]> wrote:
>
> I've almost completed an LFS Development build using DESTDIR (or whatever
> else if the package doesn't support DESTDIR) style installation. Though
> I might hit some bumps in the last few remaining packages, I'm writ
Bruce Dubbs wrote these words on 03/31/08 10:19 CST:
> Looks interesting. Where do you put your DESTDIR? Is it a part of the
> chroot partition? You said you use scripts. Can you post a typical script?
I suppose I should qualify "scripts". Actually, there is only one main
script I use to copy
On Mon, Mar 31, 2008 at 10:19:20AM -0500, Bruce Dubbs wrote:
>
> The implication of going to DESTDIR for LFS would imply doing the same
> for BLFS. Some of the BLFS packages are not DESTDIR friendly. I can't
> remember which ones off the top of my head, but I do recall some that
> ignore DEST
On Monday 31 March 2008 09:53:00 Randy McMurchy wrote:
> I've almost completed an LFS Development build using DESTDIR (or
> whatever else if the package doesn't support DESTDIR) style
> installation. Though I might hit some bumps in the last few remaining
> packages, I'm writing now to see if there
>
> I'm not trying to push this on anyone, I'm only saying that I can
> help if the community sees this as a direction we may go towards one
> day. Many others including Dan, Tushar, et. al. may be willing to
> assist or contribute as well.
>
> Thoughts from others?
>
If at all possible whil
taipan wrote:
> Bruce Dubbs wrote:
>> The implication of going to DESTDIR for LFS would imply doing the same
>> for BLFS. Some of the BLFS packages are not DESTDIR friendly. I can't
>> remember which ones off the top of my head, but I do recall some that
>> ignore DESTDIR, at least partially.
On Mon, Mar 31, 2008 at 8:03 AM, Randy McMurchy
<[EMAIL PROTECTED]> wrote:
>
> Actually, everything above is not true. First, I meant the creation
> of DESTDIR/usr/share, not DESTDIR/share and more importantly, the
> creation of the final /usr/share/info/dir file is done in place.
> This file (
Bruce Dubbs wrote these words on 03/31/08 10:19 CST:
> Looks interesting. Where do you put your DESTDIR? Is it a part of the
> chroot partition?
I've been putting the DESTDIR directory as a subdirectory of the
root of the build tree. I only did that so when I remove the build
tree after insta
Bruce Dubbs wrote:
> The implication of going to DESTDIR for LFS would imply doing the same
> for BLFS. Some of the BLFS packages are not DESTDIR friendly. I can't
> remember which ones off the top of my head, but I do recall some that
> ignore DESTDIR, at least partially.
>
>-- Bruce
Op
Bruce Dubbs wrote:
Randy McMurchy wrote:
Thoughts from others?
Looks interesting. Where do you put your DESTDIR? Is it a part of the
chroot partition?
It can't be outside this partition. With RPM, this is typically
/var/tmp/pkgname-root/ , and with dpkg, this is always the `pwd`/debian/
Randy McMurchy wrote:
> Hi all,
>
> I've almost completed an LFS Development build using DESTDIR (or whatever
> else if the package doesn't support DESTDIR) style installation. Though
> I might hit some bumps in the last few remaining packages, I'm writing
> now to see if there is any interest in
Randy McMurchy wrote:
> Thoughts from others?
Looks interesting. Where do you put your DESTDIR? Is it a part of the
chroot partition? You said you use scripts. Can you post a typical script?
The implication of going to DESTDIR for LFS would imply doing the same
for BLFS. Some of the BLFS p
Randy McMurchy wrote:
> I also track every file that may conflict or overwrite with an existing
> file on the system. This is not intended to be a package manager,
> however, it would be trivial to create one from it (I do).
>
> Much of this is done via scripts (code snippets) that can be reused
>
Randy McMurchy wrote these words on 03/31/08 09:53 CST:
> My scripts have the complete requirements, i.e., the proper commands
> to install into DESTDIR, the modified after-installation commands to
> do them all in DESTDIR (symlinks, moving libs to /lib or /usr/lib,
> etc.), proper placement of ma
Hi all,
I've almost completed an LFS Development build using DESTDIR (or whatever
else if the package doesn't support DESTDIR) style installation. Though
I might hit some bumps in the last few remaining packages, I'm writing
now to see if there is any interest in creating an LFS branch for this
ty
On Wed, Mar 26, 2008 at 7:38 PM, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> First of all, thanks to Dan for the cluebat about how gcc bootstraps
> by default now. I didn't know that. Perhaps it could be mentioned.
I was thinking that if you're reading the book for the first time,
then having
23 matches
Mail list logo
