Le 2024-12-14 10:48, Matthias Klose a écrit :
what about having two sets of packages? one set encapsulating the bootstrap, which always stays in unstable, and one "production" set, which then migrates to testing? Would that be better to keep the bootstrap knowledge up to date?
That's a possibility, though I would keep them in the same repo and manage them using branches, and maybe keep the bootstrap packages only in experimental. We are going to need branches to maintain the gradleN packages anyway (only support and no opposition so far for renaming to gradleN, so we are going this way). But I think having the makefile as a backup build method even in production is worth considering, as it's very likely that without it some upgrades will require much more work to downgrade their build scripts so they work with the currently packaged version, if that's possible at all. It also sort of breaks the circular dependency, and I think that's good practice.
Cheers, -- Julien Plissonneau Duquène
