Hi! Thanks for the suggestions, I have updated https://pad.debian.net/p/Role_model_README.source.md accordingly. Is this perhaps now the most optimal version?
... > We have `/usr/share/doc/git-buildpackage/examples/gbp-upload` that > combines sign, tag, push and upload. Looking at https://sources.debian.org/src/git-buildpackage/0.9.35/examples/gbp-upload/ and other scripts in the directory I see they are mostly just wrappers for dput && gbp tag && git push. If there was a direct "gbp upload" command that users could trust will always do they right thing, I could recommend it, but right now I don't feel it makes sense to recommend an additional script as it adds yet another layer of abstraction, and it is hosted in folder "examples" which does not instill confidence that it is something people should actually use, at most just read and copy/modify for their own use. If we ask people to take a script and modify it to their own use, then its not really simplifying the process.. I hope to get to a point where there is just one README.source.md that for a given package is *the* correct way (or at least the most optimal and recommended way) to handle that packages' lifecycle. _______________________________________________ git-buildpackage mailing list [email protected] http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage
