Sean Whitton writes ("Bug#1127616: developers-reference: should document using
git-debpush to upload"):
> Back when I worked NEW: I very often wanted to see the list of files
> installed by the package, and the full, expanded list of binary package
> relationships. Rarely, I would actually look inside the .deb.
>
> These are real needs for NEW review.
Right.
> I think one source of opposition for autobuilding packages before they
> go into NEW is that the DFSG team won't yet has asserted/confirmed that
> the license permits autobuilding. But, well, we already have Salsa CI,
> so I think that is not worth blocking on.
Indeed.
I don't know much about how the autobuilding system works but I would
love it if someone who did understand that would figure out how to
make this work.
If this is hard to organise with dak etc., one option would be a
dedicated git-based autobuilder attached to the tag2upload service.
That would somewhat be less useful to Debian as a whole, though,
because it would enable source-only NEW uploads only via tag2upload.
Having said that, it is tag2upload where the difference is *most*
stark between (a) performing a source-only operation on the uploader's
machine and (b) the uploader building binaries. So such a
tag2upload-only solution would be worthwhile if we cann't have a
general solution.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
