On 03/23/18 15:15, Toshio Kuratomi wrote:
> Something that occurred to me last night, rather than a conditional on
> Fedora version, is there a macro that we could provide to mean python2
> is available in this Fedora version? That way packagers wanting to
> support their packages on the versions of python that the platform ships
> can conditionalize on that imstead of fedora release (which is variable
> depending on whether someone picked up and drops support for the
> orphaned python 2 package)
I'm not sure how useful that would be. Wouldn't we want that not only
for the python2 package, but also for other dependencies?
Django's py2 subpackage is dropped already. Should there have been a
macro advertising that?
Also, we want to *avoid* breaking everything at once. Providing a flag
that gets flipped at one moment wouldn't solve much.
_______________________________________________
Depends on what the groups of packagers want... A macro for Django would definitely have given an easy option for packagers to take advantage of. Otoh, how far in advance was the Django removal telegraphed and how much chance was there that a new maintainer would pick it up? It doesn't do as much good for a package that is going to definitely drop support in the very next release as it does for a package that is going to drop support two releases from now, maybe, unless someone decides to pick it up, even at the last minute, perhaps only after they realize it's been removed from the repository....
Why do we want to avoid *breaking* everything at once? I can see us wanting to keep things *working* as long as it makes sense to the set of packagers that care (which I think adding the macro would aid in) but it doesn't feel like actively designing things to break a little at a time is helpful to anyone. Users can't count on things working from release to release and packagers have to do more work to keep the pieces they care about working.
-toshio