Packaging a Fork of a Python Library (Suds)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

Suds [1], a Python Library for using SOAP web services (Fedora package: python-suds), has been unmaintained for about 3 years or so. There is a relatively active fork, suds-jurko [2], that has, among other things, Python 3 support. Thus, I would like to package suds-jurko for Fedora.

Would it be better to:

A) Package suds-jurko as a new package (and then dependent packages could move over to use suds-jurko at their leisure). If this is the recommended approach, is there a recommended mechanism for having multiple python modules with the same name? Rename the fork's module to 'suds-jurko' and packages that wanted to use the fork would have to be updated to import the alternative module name?

or

B) Replace python-suds with the jurko fork and force all dependent packages to move over at the same time. If this is the recommended approach, is this big enough to qualify as a system-wide change? There are about a dozen dependent packages, according to repoquery.

Thanks,
Scott

[1] https://fedorahosted.org/suds/
[2] https://bitbucket.org/jurko/suds
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux