Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: rfc: locations of binaries and separate /usr
Date: Mon, 02 Jan 2012 06:45:13
In Reply to: [gentoo-dev] Re: rfc: locations of binaries and separate /usr by Duncan <>
On 01/01/2012 09:39 PM, Duncan wrote:
> Olivier CrĂȘte posted on Sun, 01 Jan 2012 15:17:50 -0500 as excerpted: > >> On Sun, 2012-01-01 at 12:46 -0600, William Hubbs wrote: >>> I don't think the /{bin,sbin,lib} and /usr/sbin directories should be >>> deleted. >>> >>> However, what I would like to see is that the package maintainers would >>> be responsible for creating any compatibility symlinks their package >>> needs, not portage. I don't think it is a good idea to have portage or >>> any package manager controling the migration. >> >> The other option is to do mv /bin/* /sbin/* /usr/sbin/* /usr/bin; and >> then create symlinks from the other dirs to /usr/bin.. That can be done >> in big move, it's the way Fedora is going to do it. > > That's what I had in mind, and in fact have already been thinking about > trying, here. > > Which is why I don't really like the idea of packages placing symlinks, > since then it'd likely be the symlink copied last, overwriting the actual > binary with the symlink... pointing at itself due to the symlinked dirs! > > Which is why I suggested a portage feature that would detect such > collisions and die before installing them, potentially overwriting the > binary with a symlink to itself!
It should not be a problem because merge of symlinks is automatically delayed in cases when the symlink target doesn't exist yet. There's a loop where it merges as many regular files as it can, and if there are any symlinks that can't be resolved then it merges them after all the regular files have been merged. -- Thanks, Zac