Hi, I strongly disagree with most of this, firstly if i'm writing a script and have a missing dep, i'd much rather push it to tumbleweed then deal with pip I want to zypper dup/up not try and think of what I need to update with pip. Secondaly in openSUSE we always encourage people to do and only say no to a contribution if we have very good reason to, we also don't expect anyone to do work for us. With that in mind id suggest a policy more along these lines which is what happens elsewhere. If someone adds a new package they get added as the maintainer in obs (For now lets just talk about non core things that aren't in SLE). At that point they are expected to keep the package up to date. If the package stops building and they don't fix it then it gets dropped as per our process everywhere else in factory, if the package has a security or critical bug and doesn't get fixed then it gets dropped. If a package is otherwise out of date and no one cares then frankly that's fine it can be out of date eventually if it gets to a point above it will be fixed or dropped. What goes alongside that is no one expects you or anyone else to keep packages that you don't want to maintain up to date which means there is only a small amount of work per package in the unusual case where we need to modify some macro etc even then generally such a change can be done in a way where not every package needs to be done at once. Cheers Simon On 11/20/20 5:47 PM, Matěj Cepl wrote:
Hello,
At the time of writing we have 538 packages in d:l:python which are out of date and require updating.
There are only two reasons why any Python package should be packaged for OpenSUSE: either it is dependency of another package in OpenSUSE, or we want to maintain it. Otherwise, if an user wants an unmaintained package, every user has pip available and they can install a package from PyPI directly.
The conclusion of these two points is that every package in Factory carries with itself some (small) cost, and there is no point in trying to push all of PyPI into Factory.
Therefore I suggest these limitations on putting new packages into Factory:
1. Every new package submitted to d:l:p (or any other official OpenSUSE project) SHALL include in its submit request message “business reasons” for including the package into OpenSUSE (either because it is dependency of some other package, or some other reason, why it is needed).
2. Everybody who wants to submit new package to OpenSUSE, MUST submit two updates of packages already in Factory from the list delivered to this list every week.
3. Packages which fail to build for sufficiently long time SHALL be removed from Factory and d:l:python (or moved to d:l:p:misc).
John, let me address you directly, because you do by far the most work for OpenSUSE Python packages. I really do appreciate how incredibly much you do for OpenSUSE, but I just don’t think it is right, when from 30+ requests on any work day, twenty of them are submissions of your new packages. Moreover, some of those packages are really questionable. For example, do we really want to maintain in OpenSUSE complete set of packages needed for accessing Fedora infrastructure? Why anybody who wants to maintain Fedora packages on OpenSUSE systems (and that include me, I have still rights for some Fedora packages) cannot just use `pip install --user copr-cli`?
Any queries and comments are welcome,
Matěj
_______________________________________________ openSUSE Python mailing list -- python@lists.opensuse.org To unsubscribe, email python-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/python@lists.opensuse.org
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B