On Sat, 2011-05-07 at 02:07 +0000, Clint Adams wrote: > On Thu, Apr 28, 2011 at 05:18:22PM -0400, Paul Smith wrote: > > It would of great benefit if fakeroot was relocatable, so that > > these paths could be set by the user: this allows us to put fakeroot > > into our build environment rather than requiring everyone to have > > their own version installed. > > Can you tell me what the use case is here?
I'm creating a relocatable toolchain: I have a makefile that knows how to unpack, possibly patch, configure, build, and install all the standard GCC toolchain utilities from source: GNU make, binutils, various libraries required by GCC, GCC itself, flex, bison, gdb. Once I have all these created I tar them up and I can store that tarball as part of a source code control system, then each individual user can untar it and use that toolchain, along with a specific sysroot that I also tar up, rather than whatever native toolchain they have on their system, giving a completely reproducible and relocatable build environment regardless of what system you're compiling on. I want to add fakeroot to that toolchain so that I can do things like unpack a Linux initramfs, add some things to it, and pack it back up again while preserving all the permissions, special attributes of /dev files, etc. However fakeroot, alone among all these tools, is not relocatable. The pathnames it uses are all hardcoded into the script at build time, so I cannot add it to my toolchain tarball, unpack it in a random workspace location, and have it work. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
