Mailinglist Archive: opensuse-kde (249 mails)

[Tejas Guruswamy <masterpatricko@xxxxxxxxx>]

On 02/04/10 12:45, Martin Schlander wrote:
> This is not the usual discussion about the OBS repository structure, but 
> about 
> what packages belong where within the existing structure when and why.
>
> Recently I've noticed a few things that I've been a bit unhappy with in terms 
> of "package placement", so I brought up the subject of repo policies on the 
> IRC meeting, and it was decided to have a discussion here on the ML instead. 
>
> What I'm unhappy with is an increasing amount of development releases like 
> BasKet, KChess, Amarok etc. in the KDE4:Community repository and in 
> KDE:Backports - these repos are pushed to casual users via the YaST Community 
> Repositories list, and should be kept relatively safe and conservative. But 
> also KDE4/Qt4 apps like Screenie being in KDE:Community instead of 
> KDE:KDE4:Community.
>
> So I think we should try to agree on some policies and rules to make things 
> clearer for packagers and users alike. Here's my suggestion:
>
> * KDE:Backports
> Newer versions of apps which are part of the official distribution. Devel 
> releases should be avoided unless there are special circumstances - e.g. the 
> betas are known to be quite stable *and* no functional stable release exists 
> *and* the app provides very important functionality (examples: K3b, Kaffeine, 
> Kile).
>
> * KDE:KDE4:Community
> KDE4/Qt4 apps which are not part of the official distribution maintained by 
> community volunteers. Betas should be avoided if possible unless there are 
> special circumstances - e.g. the betas are known to be quite stable *and* no 
> functional stable release exists.
>
> * KDE:KDE4:Playground
> Development releases (alphas, betas, RCs) and version control snapshots of 
> KDE4/Qt4 apps.
>
> * KDE:Community
> KDE3/Qt3 apps maintained by community volunteers and which don't exist in 
> KDE:KDE3. (Maybe this repo should be shut down and everything moved to 
> KDE:KDE3, since KDE:KDE3 is all community maintained now anyway?)
>
> What do you all think about this?
>   
General agreement from me, just a question: how to decide if a package
is beta if it is not explicitly stated? Does version < 1.0 mean beta? I
bring this up because for example tiny applications on kde-apps don't
have a consistent version numbering system ... the author just starts at
0.1 by default, bumps it a few times, then abandons it at 0.4 once it is
stable ...
Or does beta mean that there is a different stable released version also
available?

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