On Monday 01 March 2010 20:30:24 Tanstaafl wrote: > On 2010-03-01 1:08 PM, 7v5w7go9ub0o wrote: > > So layman users choosing alternative A. now may want to add a step; > > after moving the directory, put a soft link in the /usr/local/portage > > pointing to the new location; i.e. > > > > cd /usr/local/portage; ln -s /var/lib/layman layman > > Thanks, I was planning on doing the same thing and glad to be validated... > > Question: the news itme also mentioned the reason as something like > 'layman violates the general rule that nothing in portage should touch > anything in /usr/local'... > > Well... my local overlays (that I set up a long time ago) are there... > and portage obviously 'touches' those, so... should I move them as well?
As it turns out, portage is hard-coded to skip over @PORT_DIR/local/ for the simple reason that your personal local overlay goes there. I have $PORT_DIR here redefined to be /var/portage/ and layman goes /var/portage/local/layman/, mostly because I think FHS is a good standard and it says /usr/ should be able to be mounted read-only. In short, if you put an explicit entry in make.conf for the layman overlays, you will be fine as you are no longer relying on a default that can change. -- alan dot mckinnon at gmail dot com
