[SOLVED] binrepos.conf overrides PKGDIR value in make.conf

[sdauth]

Hello,
Maybe it has been this way for some time now but I only noticed it today.

I have several laptop pulling binaries from my main desktop.
So I noticed those binaries are now saved in /var/cache/binhost/main-binhost/ instead of /var/cache/binpkgs

On each laptop I have the following In /etc/portage/binrepos.conf

Code: Select all

[main-binhost]
priority = 100
sync-uri = https://home.lan/gentoo/main-binhost/binpkgs

and in make.conf

Code: Select all

PKGDIR="/var/cache/binpkgs"

and also:

Code: Select all

EMERGE_DEFAULT_OPTS="--jobs 2 --getbinpkgonly --binpkg-respect-use=n"

In order to never build anything but only pull binaries from my main desktop.

Is it possible to save them to the PKGDIR location, like before ?

Thanks.

[sam_]

See Portage NEWS in /usr/share/doc. The intention is to have separation between downloaded binpkgs and locally built ones (for a few reasons: it allows signature verification to be enabled just for remote binpkgs (even per-repo), it allows you to re-serve your own binpkgs without doubling up on copies of ones from another binhost, etc).

You may be able to set location = /var/cache/binpkgs in binrepos.conf but then you won't be able to safely do signature verification. Is there a reason you really want those in the same place? That will affect how much we want to support it and in what way.

[sdauth]

Thanks, it makes sense.
It is only because I have a couple of exclude for my backup app (btrbk) and I noticed it took a bit longer today. After reviewing the log, I found out it backed up this (not excluded) location.
Otherwise I don't have particular other reason, so I will adjust my btrbk config to exclude this new location.

[sam_]

Thanks for explaining. I plan on having a news item for default-enabled verification in Portage and then will mention this change in there.