Le 2025-05-12 15:04, Lucas Nussbaum a écrit :
Regarding "I don't want a gbp.conf", I think that we should aim for
DRY,
and that adding a gbp.conf in every package doesn't sound too great for
teams that maintain hundreds or thousands of packages...
Could having a way to manage "team defaults" for gbp provide some relief
here? These could maybe be distributed with the gbp package, or a
separate distribution-wide package, or by separate packages managed by
each team. The idea would be to add some logic to gbp to apply different
defaults depending on the declared maintainer of the package. Such
defaults could still be overriden by gbp.conf the same way as current
gbp built-in defaults can be.
Cheers,
--
Julien Plissonneau Duquène
