On 12/05/25 at 07:49 +0000, Holger Levsen wrote: > > Regardless of what branch names packages use today or in the future, > > they should all have a debian/gbp.conf file that defines what branches > > and packaging practices are being used *right now*. > > I dont want to use git-buildpackage and I don't want a gpb.conf. Please accept > this. Thanks.
"I dont want to use git-buildpackage" sounds a bit like "I don't want to use debhelper". There are many cases where it makes sense to standardize on workflows and tools (and accept that it reduces the number of degrees of freedom, and many using inferior tools). And there are some cases where it makes sense to use specific workflows and tools (because it gives more power to optimize stuff). Maybe DEP-14 should focus on being the debhelper of git-based packaging, and we should acknowledge that it will probably never be adopted by some maintainers or source packages. 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... Lucas
