Miro Hrončok wrote:
> [2] https://fedoraproject.org/wiki/Packaging:Deprecating_Packages
This policy is highly impractical. Any package can be deprecated without
notice, in some situations even without any kind of approval (if there is
nothing using it in Fedora yet). One needs to do a repoquery to even get the
list of deprecated packages, because they are not centrally tracked. And if
I package or review a new package, I am now supposed to check every single
BuildRequires (and maybe also its transitive Requires closure?) for whether
it "Provides: deprecated()"!? There is just no way I am going to do that.
Applying this policy to a language interpreter that is used by dozens of
useful packages that are not yet packaged for Fedora makes it even more
impractical. Let's face it: lots and lots of upstream software will NEVER be
ported to Python 3. Yet, it is still useful, and may be the only way to do
what the user needs to do. Banning all that software from Fedora is doing a
major disservice to our users!
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
