Mailinglist Archive: opensuse-kde (249 mails)

< Previous Next >
Re: [opensuse-kde] Discussion about repo policies/purposes (Att: Packagers)
  • From: Raymond Wooninck <tittiatcoke@xxxxxxxxx>
  • Date: Sun, 11 Apr 2010 14:44:59 +0200
  • Message-id: <4BC1C44B.807@xxxxxxxxx>
On 04/11/2010 11:09 AM, Karsten König wrote:

Hmm Contrib will be frozen from time to time, still I like the idea, for
Backports you could always build the Contrib:Factory for 11.2 as well etc.
Though I don't really know the current situation of :Contrib, I know it was
planned to merge with Factory but that was dropped. So is it there to stay?
Anything else to say, like currently only few maintainers or similar?

As far as I know Contrib is still there to stay, but I am not well
informed around this topic :-)

However my idea was purely to follow the naming convention and initially
a Contrib repo per KDE version.

The Contrib structure would sort that out, we could make multiple Contrib
repos like currently done in the main Contrib repo (version of 11.1, 11.2,
Factory). Though this is of course generating more maintainer work =/

Well, is this something that we really want ? As indicated I brought
Contrib up for naming conventions, but not necessary to follow the exact
structure setup. Although it would make sense if we want to provide
people with a stable setup. We could say that we have KDE4:Stable and
KDE4:Stable:Contrib which are frozen (except serious bugs, security
issues, etc). That way it would not be too much work.

In my opinion Backports and Playground should stay as they are now
(single repo setup for all KDE versions). In Playground we could have
more maintainers as that there everything would be theoretically
possible. The Contrib repo should be mainly based on SR requests, which
are accepted by the repo-wide maintainers. We could have then a few
other people maintaining specific packages (e.g. midi-related, etc).

Cheers

Raymond
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx

< Previous Next >