Cyril Brulebois <kibi@debian.org> writes:
> The problem is that apt-setup is currently working on a single
> sources.list file, and having the 60local generator work on a different
> one would likely mean reworking the debconf automaton quick a bunch. It
> could also break the CI (mostly run/monitored by the other Roland and by
> Phil, hence the explicit cc).
It seems to me that we need a new debconf setting, so that code to
migrate towards deb822 usage can be added without immediately breaking
things.
We could have e.g. `apt-setup/use-deb822-format` that might take values
like:
`no`:
everything should be in sources.list format.
Is that what we currently have, or are we already in a mixed state,
with some things generating deb822 already?
If so, perhaps this setting should just mean that other scripts can
assume that apt-setup will have produced sources.list.
'update':
use apt-get update to convert .list files
'yes-maybe':
things that know how to produce deb822 should do so,
and we get to see what breaks.
'yes':
everything should be deb822, and things producing .list style are an error
I'm thinking that most things could check for "yes*" and if that's
found, use the new deb822 code, otherwise stick with the old. There
might be a reason for also have `yes-update` as an option (do deb822 if
you can, and also run apt-get update).
I guess that things that might want to fiddle with sources.list, but can
do deb822 too, should check for sources.list.d/debian.list (or whatever
apt-setup will be creating) and behave accordingly.
That way we could get on with writing new code for dealing with deb822
format, made conditional on that setting, and do some testing. Depending
on how well that goes, might decide to set it to something other than
`no` for trixie's initial release, or a point release.
Anyway, if we have some idea of the direction of travel, I'm happy to
work on the 60local stuff, and making it viable in a deb822 world.
We can also add tests on openqa for what format actually ended up on the
installed systems, to see how we're progressing.
Cheers, Phil.
--
Philip Hands -- https://hands.com/~phil
Attachment:
signature.asc
Description: PGP signature