On 02/25/10 01:15, Sebastian Pipping wrote: > ======================================================================= > Title: Layman storage path changed from version 1.3.0 on > Author: Sebastian Pipping <sp...@gentoo.org> > Content-Type: text/plain > Posted: 2010-02-25 > Revision: 1 > News-Item-Format: 1.0 > Display-If-Installed: <app-portage/layman-1.3 > > Layman has been using /usr/local/portage/layman to store > overlay checkouts from version 1.2.3 on. As that path > was violating the concept of keeping portage away from > /usr/local the default of this storage location moves to > > /var/lib/layman > > from version 1.3.0 on. If you have never modified /etc/layman.cfg > manually before, you may be tempted to let tools like etc-update > or cfg-update blindly accept this new version of layman.cfg.
Err: /etc/layman/layman.cfg not /etc/layman.cfg Fixed: ==================================================================== from version 1.3.0 on. If you have never touched the file /etc/layman/layman.cfg manually before, you may be tempted to let tools like etc-update or cfg-update blindly accept this new version of layman.cfg. ==================================================================== > As that would hide all your currently installed overlays from layman > it's probably not what you want. Your options are: > > A) Moving > Move your current location to /var/lib/layman before upgrading Forgot about PORTDIR_OVERLAY: ==================================================================== A) Moving Move your current location to /var/lib/layman before upgrading. Also update PORTDIR_OVERLAY in make.conf accordingly. ==================================================================== > > B) A symlink > Put a symlink to your current storage location at /var/lib/layman > before upgrading layman. > > C) Configuration > Reject the path change for layman.cfg when running tools like > etc-update or cfg-update blindly. Be aware with this way you'll > have to do it for each layman update again. > > PS: This news item is a reaction to users having run into this problem > (see bug #306233). Thanks to Volker Hemmann for reporting. > =======================================================================
