| 1 |
On 02/25/10 01:15, Sebastian Pipping wrote: |
| 2 |
> ======================================================================= |
| 3 |
> Title: Layman storage path changed from version 1.3.0 on |
| 4 |
> Author: Sebastian Pipping <sping@g.o> |
| 5 |
> Content-Type: text/plain |
| 6 |
> Posted: 2010-02-25 |
| 7 |
> Revision: 1 |
| 8 |
> News-Item-Format: 1.0 |
| 9 |
> Display-If-Installed: <app-portage/layman-1.3 |
| 10 |
> |
| 11 |
> Layman has been using /usr/local/portage/layman to store |
| 12 |
> overlay checkouts from version 1.2.3 on. As that path |
| 13 |
> was violating the concept of keeping portage away from |
| 14 |
> /usr/local the default of this storage location moves to |
| 15 |
> |
| 16 |
> /var/lib/layman |
| 17 |
> |
| 18 |
> from version 1.3.0 on. If you have never modified /etc/layman.cfg |
| 19 |
> manually before, you may be tempted to let tools like etc-update |
| 20 |
> or cfg-update blindly accept this new version of layman.cfg. |
| 21 |
|
| 22 |
Err: /etc/layman/layman.cfg not /etc/layman.cfg |
| 23 |
|
| 24 |
Fixed: |
| 25 |
==================================================================== |
| 26 |
from version 1.3.0 on. If you have never touched the file |
| 27 |
/etc/layman/layman.cfg manually before, you may be tempted to let |
| 28 |
tools like etc-update or cfg-update blindly accept this new version |
| 29 |
of layman.cfg. |
| 30 |
==================================================================== |
| 31 |
|
| 32 |
|
| 33 |
> As that would hide all your currently installed overlays from layman |
| 34 |
> it's probably not what you want. Your options are: |
| 35 |
> |
| 36 |
> A) Moving |
| 37 |
> Move your current location to /var/lib/layman before upgrading |
| 38 |
|
| 39 |
Forgot about PORTDIR_OVERLAY: |
| 40 |
==================================================================== |
| 41 |
A) Moving |
| 42 |
Move your current location to /var/lib/layman before upgrading. |
| 43 |
Also update PORTDIR_OVERLAY in make.conf accordingly. |
| 44 |
==================================================================== |
| 45 |
|
| 46 |
> |
| 47 |
> B) A symlink |
| 48 |
> Put a symlink to your current storage location at /var/lib/layman |
| 49 |
> before upgrading layman. |
| 50 |
> |
| 51 |
> C) Configuration |
| 52 |
> Reject the path change for layman.cfg when running tools like |
| 53 |
> etc-update or cfg-update blindly. Be aware with this way you'll |
| 54 |
> have to do it for each layman update again. |
| 55 |
> |
| 56 |
> PS: This news item is a reaction to users having run into this problem |
| 57 |
> (see bug #306233). Thanks to Volker Hemmann for reporting. |
| 58 |
> ======================================================================= |
Archives