Re: [RFC] General Resolution to deploy tag2upload
Joerg Jaspert <joerg@debian.org> writes:
> On 17265 March 1977, Russ Allbery wrote:
>> I wish it wouldn't change what package maintainers do, but the only way
>> I think that works is to interpose a relatively complex build step
>> between the maintainer representation and the archive, which is exactly
>> what we're currently stuck on.
> Well, no. We *can* say "This new thingie *only* works this way. If you
> want it, your package has to look like this, if not, do it whatever way
> you prefer, but this new thing then is not for you". I don't think thats
> bad.
I don't think it's bad in any inherent way, but it's not tag2upload. It's
not the thing that the developers have been working on, it doesn't solve
the problems they're trying to solve, and it doesn't let people use the
workflows that they want to support.
Maybe it's a useful thing that Debian would benefit from having, but it
doesn't achieve what they set out to achieve, which is "you can use the
Git workflow that you like and are currently using (for a bunch of common
workflows and hopefully more later) *and* upload with a Git tag without
having to have the Debian-specific source package machinery locally."
That's the thing they wrote, and that's the thing they want to deploy.
"Uploading Debian packages only requires making a tarball of a Git
checkout as long as you follow this specific way of using Git" is a
different solution to a different problem. It's not bad! It has some
nice properties! But it's a very different interface for the package
maintainer than "do whatever you're currently doing but stick this stuff
in your signed Git tag and you can stop thinking about source packages."
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
Reply to: