V Tue, Mar 29, 2022 at 05:04:29PM +0000, Mattia Verga via devel napsal(a):
Il 24/03/22 09:12, Petr Pisar ha scritto:
> V Wed, Mar 23, 2022 at 05:40:28PM +0000, Mattia Verga via devel napsal(a):
>> So, now that we have side-tags to perform this kind of builds, does the
>> buildroot override existence still make sense? Is there any use case
>> that still requires BR overrides and cannot be done with side-tags?
>>
> I use overrides pretty extensively when populating new EPEL. If you have
> a deep dependency tree and the packages are scattered among many maintainers,
> it's much faster to use an override than to block depending packages for
> a week. Side tags also do not work there because every new package would reset
> the testing period. And if I'm not mistaken non-proven packagers cannot edit
> other's updates. And I don't count communication overhead. People would end
up
> mixing various side tags and crosstagging builds.
>
Maybe BR overrides usage should be restricted only to users with special
needs (users in provenpackager or releng groups), while "normal" users
should be forced to take the side-tag way?
I'm not sure. There are more people in Perl stack who do it and are not
proven
packagers. Maybe EPEL in its initial phase should work more like Rawhide, i.e.
without updates-testing repo.
-- Petr