Mandag den 7. juni 2010 15:29:28 skrev Sven Burmeister:
There are two types of users, update users and testing users.
Update users might want: - Only security updates (recommended) - Backports only (minor risk) - minor KDE version updates (minor risk of regressions) - major KDE version updates (normal risk of regressions) + revert to KDE packages that came with [user's distro]
Test users might want:
(- help testing security updates) - help testing the next openSUSE version (risky) - help testing the next KDE version (very risky)
I also think there are two types of users: 1) "civilians" (90-95%) 2) geeks and fanboys (5-10%) Civilians will just use the kde version shipped, and maybe add Backports and Community/Extra - which is easily done with clicky, clicky in yast community repositories. Anyone who doesn't think this is good enough ceases to be a civilian by definition - and therefore in my mind the user immediately forfeits his handholding and whining privileges.
The above options could be put into a systemsettings module. The user would not need to know anything about the repo structure, he just needs to know what he wants to do. The GUI enables the KDE Team to add more information and warnings while easing the testing and usage of KDE packages. And it does not have to worry about the repo structure being understandable by users. The systemsettings module would use kupdateapplet to check for changes and notify the user on KDE login.
The actual repository structure could then be something like:
(STABLE) KDE43 -- 11.1 -- 11.2 KDE44 -- 11.1 -- 11.2 KDE45 -- 11.1 -- 11.2 Backports -- 11.1 -- 11.2 Factory -- 11.1 -- 11.2
I see a number of issues. * Who would package and maintain the 44 and 45 repos? * Who would write and maintain such a systemsettings module? * The average user would always underestimate the risks and inconveniences and select all kinds of updates he doesn't need, which will cause more problems than they solve * User support would be a impossible with such a large number of different kde versions and flavours in circulation In my opinion this would be using waaaaay too many resources to please small - albeit very loud - minority - with little benefit to the distro and the project. We need to be careful with resources, and I think what we already have is pretty great. Civilians can add Backports and Extra/Community easily. Geeks and fanboys should be able to figure out how to add Playground, Factory or Unstable manually, and if they can't, then they're probably better off not using these repos in the first place. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org