Bug#1007717: Native source package format with non-native version
On Thu, Mar 17, 2022 at 11:57 AM Russ Allbery <email@example.com> wrote:
> source package format
While everyone is receptive to new labels, I prefer "upload format" or
"archive format". Either one helps us to distinguish the intermediate
product from any workflow objects a maintainer may have.
> single tarball as a source package format
It is also not necessary to "define" unpatched sources in the archive
by how many tarballs they have, or any tarballs at all.
In fact, I wrote a manifest utility that could one day replace tarball
signatures with per-file hashes. The latter remain useful even when
sources are repackaged, because manifests can be cryptographically
daisy-chained in a "chain of custody." Of course, they would be more
often used for patched upload formats.