On Wednesday 07 of April 2010, Martin Schlander wrote:
Onsdag den 7. april 2010 15:51:49 skrev Lubos Lunak:
So there is a place for second repo, which would be 'what is not in o:F' and contain stuff that would be worth placing at least there. But 'Community' is not a good name for that. Additionally, since it is provided in Yast, I would really expect at least some assurance of quality there[*]. How does KDE:KDE4:Community actually currently work? The repo-wide maintainer list is pretty long and I don't know many of those people, to me it looks like it's some free-for-all repo. Or are others here really fine with providing such a repo in Yast?
I think it's very important to have the repo and offer it via yast - no matter what it's called. It enables us to provide more packages as well as new ones appearing with very little hassle for users - like e.g. Synaptiks[*] which didn't exist in time for 11.2 but fills a gaping hole in the kde package set. Therefore having such a repo in yast is a huge asset to the distro - especially from a casual user point of view.
I think nobody is arguing against that.
We just need a bit of guidelines and some packager discipline to make it a little less messy and risky.
And this is my problem (the lack of this, that is). Let me put it differently. There is KDE:Backports, which is newer versions of what is in the distribution. We can have one more, let's call it KDE:Extra, which would be KDE apps that are not part of the distribution. There's no problem with that. The problem is that KDE:KDE4:Community currently serves this role, and, as far as I understand it, has almost no rules or review (I'm right on this, am I not?). I think we should do a bit better for a repository that is offered to users directly in Yast. So what I propose is that KDE:Extra is created and the workflow is not free-for-all. I.e. repo-wide maintainers are not handed out to everybody but only to some people with certain trust and experience. And by that I don't mean that I myself want to rule the repo with an iron hand, but this should simply assure certain review and prevent obvious screwups like the recent libqt4 inclusion in KDE:KDE4:Community. Repo-wide maintainers would be people willing to take care of the repo as a whole. If somebody would want a package there, they would ask on this list, then do a submit request resulting in creating the package in the repo. Further updates would be by additional SRs or, if trusted enough, they would get maintainer only for the package. Opinion on this? I'm not sure what would be less work, simply keeping KDE:KDE4:Community and doing a cleanup in it to make it this repo, or start from scratch and copy over things.
And it needs a bit of janitorial work - with kcm_touchpad and plasma-theme-air which should both clearly be removed being my current favourite annoyances.
I'm considering looking into whether such janitorial work is managable for someone with my very limited skillz.
[*] However the adding of synaptiks to factory seems to have meant it has disappeared from Community and therefore is currently not built for 11.2+4.3.x users :-(
You can copy it back and build it only for build repositories which do not include it from KKFD yet. I assume that would be similar also for the packages above that you suggest should be removed. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org