On Sun, Jul 13, 2025 at 06:04:45PM +0200, Michał Górny wrote: > Hi, > > GURU -- much like Sunrise of the old days -- has a policy of including > only packages that aren't in ::gentoo. I'm wondering if we should put > that into a formal key in metadata/layout.conf that could also be used > in other repositories. Something like: > > # This repository only permits packages that aren't in any of its > # masters. > new-packages-only = true > > We'd use that in pkgcheck to report "duplicate" packages, and perhaps it > could also cause package managers to always prioritize packages from > masters, independently of version. > > WDYT? I like the idea; but the principal of least surprise worries me. +1 on warnings based on it. -1 on prioritizing from parent repos.
Example 1: Time=0: overlay ::A is bleeding edge, and has pkg/cat-0.0.1, possibly right as upstream releases it. At this point, it passes pkgcheck CI. User does emerge pkg/cat, gets the overlay version. Time=+1d pkg/cat is added to ::gentoo, with slightly different USE flags or config options [possibly to a skipped optional dependency that is not yet in ::gentoo]. At this point, the CI on ::A starts to fail. The same user is doing a rebuild, and rebuilds pkg/cat; they get pkg/cat from ::gentoo, which now has different behavior. Example 2: Similar to above, but with pkg/cat-9999. Should the package manager downgrade the user? > > -- > Best regards, > Michał Górny -- Robin Hugh Johnson (then/he) Gentoo Linux: Dev, Infra Lead, Foundation Treasurer E-Mail : [email protected] GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
signature.asc
Description: PGP signature
