Re: Choosing a stable+2 release name BEFORE the freeze
Neil Williams wrote:
> Most of these packages go backwards in time, not forwards. We
> can test that previous releases work with the tools - future releases
> are likely to break stuff and you may well need new options or new
> behaviour to work with future releases.
>
> Certainly had this problem with multistrap - apt 0.8.x was updated
> during the freeze and broke many patterns of previous behaviour and
> led to a lot of work to get multistrap in Squeeze to even work with
> Squeeze, let alone Wheezy.
The thing is, my package here isn't debootstrap or multistrap. It USES
deboostrap only, which is very different. Don't you think it's really
probable that, when Squeeze will be out, and Wheezy exists, there will
be at least a backported version of {deboot,multi}strap available that
will be able to bootstrap testing when running stable? If you tell the
above, then why debootstrap in stable even has the option to boostrap
SID or stable+1? It doesn't make sense to me why debootstrap would have
the option, and other packages shouldn't.
Anyway, all this isn't a so big deal, I just wanted to share my thoughts
with others. :)
Thomas
Reply to: