Am 10.11.2015 um 18:39 schrieb Richard Brown:
On 10 November 2015 at 18:33, PGNet Dev <pgnet.dev@gmail.com> wrote:
And, what's "improper" about the maintenance of packages currently in the devel & non-home repos?
Devel projects & all non-home repos are not tested. Our distributions are.
Devel proejcts & all non-home repos do not have to follow our packaging policies
Thats the reason for not submitting everything to Factory / Leap
and quality standards. Our distributions do
I do not buy that "quality standards" argument. I hold my packages in e.g. "vdr" and "vdr:plugins" projects to high standard. But vdr:plugins simply contains the things that I do not use myself or where I know that the code is not well maintained. The more commonly used things are in "vdr" or some of them even in Factory / Leap. But e.g. constant annoyance because I, as the single maintainer of these packages, using absolutely descriptive patch names and patch headers (either by using the git patch or by writing a descriptive patch header) refuse to add an additional patch tag, leads me to not bothering submitting those to Factory. (I'm not questioning that there are projects like GNOME:Factory or whatever, where people like patch tags and find them useful, but for me they are just annoying).
Devel projects (and the majority of non-home repos) exist for a primary purpose of *developing* packages *before* their inclusion into Tumbleweed
No, they exist so that people can provide quality software without the overhead of dealing with the factory policies.
By definition that means Devel projects and non-home repos are going to be *BROKEN* at some point
No. Only badly maintained ones.
Because that is precisely the place where our developers have SO they can break stuff before it hits one of our distributions
Maybe that's how you work. I have extra projects where I test the really experimental stuff before submitting it to vdr and vdr:plugins. If the best I could do was to randomly break stuff for my users, I would immediately put the packages up for adoption.
In fact, if those projects are NOT breaking from time to time, then I argue that the maintainers are doing something wrong
Thanks for your encouraging words!
And the same will be true for 42.2..if people want those packages in our next release next year, get them in Tumbleweed now, and make sure they get into Leap 42.2 next year.
Then get rid of some of those stupid policies. But your way of looking at things explains a lot of the sorry state some parts of the distributions are in... -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org