1 |
On Tue, Jan 14, 2020 at 5:05 PM Paul B. Henson <henson@×××.org> wrote: |
2 |
> |
3 |
> I recently installed a new server, and noticed that it is using |
4 |
> /var/cache/distfiles rather than /usr/portage/distfiles. looking at the |
5 |
> documentation, it seems that is the new default, and it says "new |
6 |
> installations" will use it. I have older servers which are still using |
7 |
> /usr/portage/distfiles. None of them have DISTDIR configured, so I am |
8 |
> curious how portage is deciding between "old" and new"? If I wanted to |
9 |
> migrate my older boxes to the new location without explicitly setting |
10 |
> DISTDIR on them, what do I need to change? |
11 |
|
12 |
The portage ebuild has some code that automatically patches |
13 |
/usr/share/portage/config/make.globals for existing installs. You can |
14 |
update the setting there. |
15 |
|
16 |
Alternatively, you can perform the following steps to make the portage |
17 |
ebuild update make.globals for you. |
18 |
|
19 |
1. Set DISTDIR to anything other than /usr/portage/distfiles in |
20 |
/etc/portage/make.conf |
21 |
2. Re-install sys-apps/portage. |
22 |
3. Remove the DISTDIR setting from /etc/portage/make.conf. |
23 |
|
24 |
From then on, portage will no longer patch the default DISTDIR setting |
25 |
in make.globals. |
26 |
|
27 |
Reference: https://gitweb.gentoo.org/proj/portage.git/tree/lib/portage/_compat_upgrade/default_locations.py?h=portage-2.3.84 |