On 17.06.24 19:50, Simon Richter wrote:
They all fall short, because git cannot represent the data model of Debian source packages
Well. I wouldn't go that far. A Debian source package, after all, is simply a directory tree with a bunch of files in a debian/ subdirectory. There's nothing magic about any of that. You check it out and run "debuild -b" and "dput". Done.
Where git does fall short is mirroring the pre-git and extra-git state of the world, including Upstream tar files and quilted patches and whatnot. That's hardly unique to Debian, though; just look at the myriad of tools that surround the Linux kernel's development model. While we don't have a single tree, we compensate with multiple Upstream models, plus multiple dictators-for-life ^W maintainers instead of one Linus Torvalds.
There are different trade-offs to be had here, which results in different magic incantations you need to invoke to create a source package. Some of them are built into dgit. tag2upload simply invokes that tool.
I'm willing to assume that, if in the future somebody decides to drop the ability to execute one of these magic incantations from dgit for whatever reason, we'll check the archive for packages that require this specific incantation and talk to their maintainers how to move forward.
Again, that's dgit's part of the equation, not t2u's proper. Thus I don't see why the existence of this admittedly-thorny problem should affect our decision to go ahead with deploying tag2upload.
-- -- regards -- -- Matthias Urlichs
OpenPGP_signature.asc
Description: OpenPGP digital signature
