On Mon, Apr 08, 2024 at 09:44:55PM +0900, Simon Richter wrote: > > I don't mind what other people do, but I worry that conversations like > > this seem to take the new thing as so self-evidently better that > > no-one can reasonably complain about them being made a > > requirement. Well, we don't all think it's better, and I wouldn't > > enjoy seeing 'packages must be in Salsa' made a requirement, for > > example. > > What people seem to be missing is that the Debian archive *is* a version > control system. We are not missing it. > Stacking another VCS on top of it leads to a lot of annoying artifacts, > because there is no sensible metadata mapping between them -- what is > metadata in Debian becomes data in git, and another metadata layer is added > on top of that, and what is data in Debian must be run through a filter to > make it accessible to git for efficient handling, so part of it gets > converted to metadata. > > The result is... not ideal, because the resulting workflow is neither a > Debian nor a git workflow, but a mix that requires users to be aware of the > state of two systems at the same time. We know, and we are sad about this, but we see the benefits it brings so we tolerate the rough edges and data duplication and hope for a better future when the workflows are improved. Some of us make proposals for better workflows from time to time but this is Debian. > Testing a package requires me to commit everything into git first, so I > have to remember to squash all these commits later.\ At least gbp doesn't require anything like this (unless your "testing" requires Salsa CI which is another story). > What would make sense would be a git based format that is designed around > the requirements for package maintenance, and where internal consistency can > be enforced by upload hooks -- for example by storing metadata out-of-band > in a separate branch. We know. It was rejected as Debian doesn't want to store random data as a part of a repo history because of DFSG, or something like that. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature