On Mon, Nov 11, 2019 at 5:28 AM Mickaël Bucas <[email protected]> wrote: > > My two systems are currently using the old locations. > Is there a documentation about the way to migrate to the new locations > without breaking things ? > The profile links comes to mind but other things are probably necessary ! > > Has anyone already done the migration ? > In this case do you have advices or warnings about it ?
Moving both paths around have been trivial for a very long time. Both are completely disposable when you think about it so there isn't much you can do wrong. Just set DISTDIR and PORTDIR anywhere you want. You can optionally move the existing files to those locations, but if you don't portage will just re-create everything on the next emerge --sync and re-fetch distfiles as needed. If you're ever concerned that something bad has happened to either directory you can always just wipe it out and let portage repopulate it. I personally keep both in /var/cache and am not a fan of the non-LSB /var/db in general, as I think the repo basically is a cache. However, this was not the majority view. In any case it is just a default so it really isn't a big deal - any user can put both of these directories anywhere they prefer. Ditto for binary packages, logs, etc. The only thing you'd need to be careful about migrating is the installed package metadata, as that can't be easily regenerated. I also keep a /usr/portage symlink because I must be getting old. :) Some tools also have that path hard-coded. The one thing I do strongly recommend is not nesting DISTDIR inside PORTDIR. That really wasn't a great design from day 1 and I don't think anybody disagreed with separating them. I'm not sure how much I like $PORTDIR/metadata being where it is either, but I can at least see the argument of keeping syncs of it and PORTDIR atomic and that is an easy way to accomplish this. -- Rich
