[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1107137: Distinguish "native source packsge" from "native version number"



Hi,

On Wed, 04 Jun 2025 08:22:46 -0700 Russ Allbery <rra@debian.org> wrote:
[1] Sneak preview: none of the subsequent discussion has substantively
    changed my opinion as expressed on the original TC bug in 2022:
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007717#50

I agree with pretty much everything you wrote back then. In particular, I find your proposal still relevant:

On Tue, 15 Mar 2022 21:22:09 -0700 Russ Allbery <rra@debian.org> wrote:
What I would propose is to separate these concepts cleanly so that we can talk about them in a clearer way. We should define native and non-native packages in terms of version numbers, and allow both native and non-native packages to use single-tarball source package formats. We may want to steer people away from using the single-tarball source package format for the *normal* case of packaging upstream software, but I think it's well within the sorts of trade-off decisions that packagers already make and there are cases where a single tarball source format makes sense.

I think this is covered by the TC decision. If not, we should make it so.


Cheers
Timo


--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

Attachment: signature.asc
Description: PGP signature


Reply to: