Re: using testing/stable/unstable names with cdebootstrap
Vincent Danjean <firstname.lastname@example.org> writes:
> Goswin von Brederlow wrote:
>> Ritesh Raj Sarraf <email@example.com> writes:
>>> Is there a reason to not use stable/testing/unstable as the names in
>>> config/suites file ?
>>> Currently it only has code names like etch/lenny/sid.
>> Does it matter anywhere? You can use testing as suite name on
>> invocation and it will see that testing currently is lenny and use
> How will it know the corresponding between the 'hard' code name (ie etch)
> and the logical code name (ie stable) ? Do not forget that this is the
> *same* package that will be in unstable, then testing, stable and oldstable.
> So this cannot be hardcoded in the program.
> Perhaps cdebootstrap can look at somewhere on the net (I do not use
> cdebootstrap myself, so I do not know). But this feature (allowing testing, ...)
> cannot be solved just by adding aliases directly in the package itself.
> Best regards,
That is really simple. You parse dists/testing/Release and got the
codename. Cdebootstrap already does this just fine afaik. At least you
can bootstrap a testing and it will use lenny and so on.