Sean Whitton writes ("Bug#848931: dgit: please add a configuration variable
that prevents me from accidentally doing a non-source-only upload"):
> Good idea. This option should be ignored when --new is present.
I was thinking about this some more and I wonder if a different
approach would be better.
If we're doing a source-only upload, the user might not want to do
binary-build-for-upload at all. It is only binary-builds-for-upload
that need to be done in a clean chroot: source packages can (I think,
and dgit relies on this) safely be manipulated in the user's working
environment.
So I was thinking that maybe there should be a `dgit push-source'
subcommand which does not depend on the existence, or look for, any
previously built artefacts. It would build the source package afresh
(a la dgit `build-source') and upload it, in one subcommand.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
