Il giorno gio 20 giu 2024 alle ore 12:43 Aigars Mahinovs <aigar...@debian.org> ha scritto: > On Wed, 19 Jun 2024 at 12:57, Gerardo Ballabio > <gerardo.balla...@gmail.com> wrote: > > 1) is the source of a package the current version of the code? [*] > > 2) is the source of a package the complete history of the project? [**] > > That is a very different set of questions and that is based on a false > premise.
I might have misunderstood Paul's questions. If so I'm sorry (if Paul wishes he could explain what he actually meant), but I think that my questions are relevant too. > History before the upstream release commit does not really matter > anymore in the source code context. If one > would shallow clone the git repo with depth to at least the last > upstream merge commit, they will get the same > results in generating the Debian source package and in all following steps. > > Using git for maintenance does not require keeping or shipping the > *entire* history of the project. Just the latest > iteration is enough. Do I understand correctly that, in reference to *my* questions, you are saying that "the source is the current version"? > The questions that Paul wrote are very different: is the specific > format that Debian chose to package the source > code for consumption inside Debian toolchain considered to be *the* > source for software, or is it just an > intermediate technical artefact of the process and the *actual* source > of the software is whatever VCS or workflow > that the Debian and/or upstream developer is using to actually manage > and modify the software. That is indeed orthogonal to my questions. To this, my answer is that both are possible means to distribute "the source files" and I'm not particularly concerned with that. I guess that if I were going to do actual development I'd prefer the VCS, while if I just wanted to build the package I'd choose the Debian source. There is probably no single format that is the best choice for all needs. Gerardo
