Probably bad form to reply to my own post, but, hey... Actually, while I think this idea has merit, there is a flaw which can be summed up in one word.
Dependencies. I'll go away and think a little more about it. David Shaw On 24/07/11 15:39, David Shaw wrote: > First of all, please accept my apologies if what I'm about to write > seems rather incoherent or is just plain impractical - I'm not a linux > guru (candidate for 'Understatement of the Year' there :-) ) and don't > really know what I'm talking about :-) > > Anyway... > > I've been thinking about package management and, having read the hints, > I feel that a combination of package users and fakeroot fits my needs > the best. However, there seem to be a few problems with fakeroot and > packages hardcoding directories into the compiled programs so... > > Is it possible/feasible/(desirable?) to install the tools needed to > compile and install a package into a directory other than the norm (say > /fr/<whatever> for 'fakeroot') and then create links in the appropriate > places to the installed files (so that the system doesn't start > complaining when they aren't where it expects them to be). You could > then chroot into the /fr folder to compile/install the package as normal > and then copy the files you want over into the 'real' system after > verifying that the install has gone OK and not done anything nasty to > the system. > > Does that even make sense? > > David Shaw -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
