Hi all, On Fri Aug 16, 2024 at 10:31 AM CEST, Guido Günther wrote: > It's never been a lack of motivation (I use DEP-14 in about all > projects). More a lack of time to figure out a proper migration path.
In #829444 it has been proposed the addition of a new "layout" option to gbp.conf, which would tell git-buildpackage which layout to follow, allowing for a graceful migration. I've been thinking about a different approach though. What about adding a warning to git-buildpackage when `debian-branch` and `upstream-branch` are not set in gbp.conf? Compared to the `layout` option, it would have the following benefits: - People already following DEP-14 don't have to do anything (big benefit in my opinion) - It would (probably) be easier to implement in gbp I also see the follwing cons: - We'd have to hardcode "debian/latest" and "upstream/latest" everywhere, which isn't pretty - Maintainers may be less prone to change branch names since having `debian-branch = master` doesn't look as bad as having `layout = legacy` After giving enough time to people to fix the warning (either by switching to DEP-14 or by keep using their own custom branch names for whatever reason), git-buildpackage can be switched to use DEP-14 branch names by default. How does it sound to you? Am I missing something? Bye!
signature.asc
Description: PGP signature
