diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
| commit | 4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch) | |
| tree | ba5f07bf3f9d22d82e54a462313f5d244036c768 /metadata/news/2010-02-28-layman-storage-path-change | |
reinit the tree, so we can have metadata
Diffstat (limited to 'metadata/news/2010-02-28-layman-storage-path-change')
2 files changed, 48 insertions, 0 deletions
diff --git a/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt b/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt new file mode 100644 index 000000000000..5726373ce128 --- /dev/null +++ b/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt @@ -0,0 +1,41 @@ +Title: Layman storage path changed from version 1.3.0 on +Author: Sebastian Pipping <sping@gentoo.org> +Content-Type: text/plain +Posted: 2010-02-28 +Revision: 2 +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 touched the file +/etc/layman/layman.cfg manually before, you may be tempted to let +tools like etc-update or dispatch-conf 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 + 1. Move your current content to /var/lib/layman. + 2. Update PORTDIR_OVERLAY in /var/lib/layman/make.conf accordingly. + 3. Make /etc/make.conf source /var/lib/layman/make.conf. + 4. Set option "storage" in /etc/layman/layman.cfg + to "/var/lib/layman". + + 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 dispatch-conf. 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. diff --git a/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt.asc b/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt.asc new file mode 100644 index 000000000000..fbbc34c6aad5 --- /dev/null +++ b/metadata/news/2010-02-28-layman-storage-path-change/2010-02-28-layman-storage-path-change.en.txt.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.14 (GNU/Linux) + +iEYEABECAAYFAkuOvSAACgkQsAvGakAaFgDdGQCgjQyWt7Kwyh1oz7rxjQPQwOhZ +NjUAoJyuoTYVBDiHNGWs8oUO9N23DTDD +=xNpZ +-----END PGP SIGNATURE----- |