Gentoo Archives: gentoo-dev

From: Sebastian Pipping <sping@g.o>
To: gentoo-dev@l.g.o
Cc: "pr@g.o" <pr@g.o>
Subject: [gentoo-dev] [rfc] Criticial news item "2010-02-25-layman-storage-path-change" (GLEP 42)
Date: Thu, 25 Feb 2010 00:15:52

As a proper solution to bug #306233 [1] I have prepared a draft for a
related glep-42-style [2] news item, my first such item ever.  This is
my request for review.

If I don't hear anything for the next 72 hours I may put it online, as I
understand the GLEP.  If you'd need more time for a proper review just
let me know.

Here we go:

Title: Layman storage path changed from version 1.3.0 on
Author: Sebastian Pipping <sping@g.o>
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


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.
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

 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.

Thanks for your help,