On Sat, 9 Jul 2011 11:48:23 +0200 Johannes Schauer <j.schauer@email.de> wrote: > On Sat, Jul 09, 2011 at 10:34:27AM +0100, Neil Williams wrote: > > Johannes Schauer <j.schauer@email.de> wrote: > > > It is because of fakechroot. A symlink you create like this: > > > > > > sudo chroot mychroot ln -s /foo bar > > > > Have you tried: > > > > ln s /foo ./bar > > or > > ln -s ./foo ./bar > > Those were just examples. I was talking about all the symlinks that get > created by the configuration step and I wanted to point out that every > script, creating absolute symlinks will have this behavior. It is not > about me creating one single symlink. Also, relative symlinks dont have > this behavior in fakechroot. OK, you're talking about symlinks created by the package maintainer scripts during package configuration. Those can't be handled in the same way as multistrap handles /lib64, that's true. Probably worth stating that next time. ;-) It is also worth noting exactly which packages are involved in these problems because very few should actually end up making symlinks which could escape the top level directories like /usr, /bin, /lib or /etc. Start a Wiki page and get this out in the open. Name and shame the packages, draw attention to the problem and get people talking about *why* this is happening. If there are genuine arguments, fine - problem is that a lot of these could just be shortcuts and convenience code which can be improved. Once you've got the data, start a discussion on debian-devel@l.d.o and see what comes out. You might actually get some of these things fixed properly. It takes time but it must be done. However, be absolutely clear and precise when discussing this - if you think my reaction was aggressive, you will get roasted alive by some of the people on -devel if you describe things the way you've done in previous threads and in this one so far. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgp24aayjTP41.pgp
Description: PGP signature