Re: Future requirements for specifying supported Python versionsand transition support
"Andreas Barth" <aba@not.so.argh.org> wrote:
>* Scott Kitterman (debian@kitterman.com) [100626 23:51]:
>> There is a bit of difference over how to specify which versions to build for,
>> but if we don't need to expose it externally (and I don't see a case for
>> this), then it's an internal matter for package build systems as long as they
>> support a requirement that arch: any packages be binNMUable for new Python
>> versions.
>
>There are pre-ideas that we might be able to binNMU arch=all-packages
>as well - nothing that will come too early, but it might be useful to
>not depend on the fact that we only binNMU arch=any.
>
No. We don't plan to depend on this. Arch all binNMU would be quite welcome and would help us solve some other issues around making Python transitions easier and more robust.
Scott K
Reply to: