On 10/28/2016 10:59 PM, Todd Rme wrote:
On Fri, Oct 28, 2016 at 12:22 AM, Simon Lees <sflees@suse.de> wrote:
On 10/28/2016 01:55 PM, Todd Rme wrote:
On Thu, Oct 27, 2016 at 7:35 PM, Simon Lees <sflees@suse.de> wrote:
On 10/28/2016 08:01 AM, Todd Rme wrote:
On Thu, Oct 27, 2016 at 5:07 PM, Simon Lees <sflees@suse.de> wrote:
On 10/28/2016 05:05 AM, Todd Rme wrote: As for applications requiring dependencies only in d:l:py the simple policy should be anything added to d:l:py should also then be forwarded to openSUSE:Factory where it will hopefully get picked up for the next Leap release as well. If this is enforced the required deps will always be available for all repos and it won't be an issue.
Are you talking about all packages or only non-python packages? Because there are a lot of niche python tools in d:l:p that I don't think belong in openSUSE:Factory.
All packages, unless they are of no interest to anyone even those doing python development. Users shouldn't need to add development repo's to there systems especially ones like d:l:p where there is a high chance that they can completely break there system by updating with it enabled. So if its useful to any openSUSE users it should go in the distro if its not there is probably a question of does it actually need to be there still? Richard has been pushing this view far more then I but its a view I agree with (you can watch his openSUSE conference talk).
There are certainly people who hold this view, but I have seen nothing to suggest it is remotely close to a consensus view. I personally cannot emphasize how strongly I disagree with this view, and how much I think it would harm projects like d:l:p. If it becomes official openSUSE policy, then certainly d:l:p will have to follow it. But I am strongly opposed d:l:p implementing this policy on its own. Especially since it would involve eliminating hundreds of useful packages that our volunteers have been willing to package but aren't willing to go through the often months-long process of getting accepted into openSUSE:Factory. We simply don't have the manpower to get every useful package into openSUSE:Factory, even if they all belonged there (and I think many of them don't belong there).
While the legal review can take up to a month, although from personal experience its gotten better of late (Even with the haskell development project adding 1500 packages at once) It's not like its a month of hard effort required. If something is packaged reasonably well to start with and according to openSUSE's guidelines the amount of work required to get it included is pretty minimal and any issues should be resolved within 1 or 2 submit requests. If people would like help with this I and others are willing to spend time helping them fix there issues. Personally I think that packages in openSUSE development repo's should be following openSUSE guidelines and packages that are not willing to do that should be in some other sub repository like d:l:p:Playground but i'm guessing others would disagree.
I disagree with most of what you said, but this can be discussed further in the Factory mailing list. What you are suggesting is a fundamental change to the most basic aspects of how OSC is organized. I am strongly against using d:l:p as a testing ground for such a change.
Given that most of the Desktop environments including (KDE/Gnome/Enlightenment) and other repo's such as haskell and probably others that I don't know about are already doing this so d:l:p would hardly be the first or a testing ground.
Even if I liked the policy, the repo is undergoing too many other changes right now. We just don't have the manpower to additionally sift through probably somewhere around 1000 packages, figure out which one should go into factory, clean them all up, wade through the submission process, do whatever it is you propose we do with those that don't make the cut. It is probably going to take months to just get the scripts implemented, and that process is mostly automated.
Again i'm not suggesting that 1000 packages should be fixed right now at once, but if you were to adopt this policy now would be a good time to consider it given that presumably you need to go through each package to add these new macro's anyway, while doing that you could decide 1. This spec file looks in pretty good shape I may as well put in a request to add it to factory 2. This package is a long way from meeting openSUSE packaging guidelines I probably should document that in the description so users are aware and someone can come back to do the work to get it up to standard later if they desire if not its labeled and we may choose to move it to another repo later. 3. This package is old and not maintained upstream its not worth migrating it to the new macro's i'll disable the build in factory and we will slowly phase it out. None of that is much extra effort on top of what already needs to be done. I have a list of packages I use from pip that I will add to openSUSE:Factory at some point, I haven't even got to checking if there in d:l:p yet because for me using pip is far easier and less complicated then trying to enable another repo for 1-2 packages. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B