On 6/14/24 12:01, Sean Whitton wrote:
Well, to put it simply, because it's better to do things using only
signed git tags than to do something highly Debian-specific.
In what ways aren't we discussing debian-specific things anyways? I
don't understand this part. We we just type "push2upload" and it's doing
some magic behind, what's the issue? Moving the magic inside the CI is
even more hiding things than doing them in the local computer.
It is better if new contributors don't have to learn about source
packages and dput at all. It is also much more convenient for existing
contributors. Take a look at how git-debpush works -- it's really very
simple and lightweight. I think you'll like it.
Here as well, I don't understand. If we have the necessary tools to do
the way Didier did, why would a new contributor need to learn about
dput? The CI would upload for them...
As for "learn about source packages", I'm not sure what their would be
to learn, except having to configure a correct build environment. That
indeed is an impressive amount of things to learn, but:
1/ one has to learn how to build packages to be able to contribute and
2/ this isn't specific to the way we're uploading, this is a more
general issue that we should make that default tooling install easier,
like having defaults that work in sbuild and gbp-buildpackage (ie: they
don't, one has to customize a lot ~/.gbp.conf and ~/.sbuildrc to make it
useful, plus the setup of schroot/sbuild that's less than trivial). So
we're having to fix this problem, but it's IMO orthogonal to the
push2upload discussion.
So, to sum-up: I'm not convinced by the points you're mentioning.
Cheers,
Thomas Goirand (zigo)
