Tirsdag den 21. april 2009 11:57:08 skrev Daniel Mader:
May I ask why Community and Playground are separated at all? Both repos are mostly community-maintained, and surely the maturity of a package can't be derived from the repo: I've seen too many failing released versions, while at the same time I sucessfully use so-called betas.
If a package is built from svn or from release sources, that information could and should be deducted from the version/minor version of a package better than from the repo it comes from...
I am sure that users who like additional software exceeding the delivered one know what that means in terms of maintenance and maybe code quality.
I am sure most users don't understand a thing. We need to think beyond the now. For 11.2 the kde4:/community repo will presumably be available in the "Community repositories" yast module for easy adding with clicky, clicky. This class of users has no clue what git or svn means - if they even look at the version number at all before installing - usually they just expect an invisible to hand to make sure everything within their reach is idiot proof. Some officially released apps may be a bit unstable, but they're not likely to be completely broken, but even if that happens we can wash our hands and point fingers at upstream. If upstream doesn't consider something release-worthy we should generally respect that and not push the stuff it on users without proper "warning". Especially if there's not even an official beta or rc from upstream, but only pre-beta svn/git versions. Even if some svn revision works great it might break at any moment, there's no reason to put unsuspecting users through such a rollercoaster. Also the split better allows packagers to provide both stable/released versions _and_ devel-versions for the same apps, without things becoming too messy. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org