I suggest to repurpose KDE:Community: Since oS adopted a 8-months cycle we will frequently encounter skipped SC releases. Put into KDE:Community: UNSTABLE, community-supported point releases (like KDE SC 4.4.5), and community-supported major releases (SC 4.5). Markus On Monday 12 July 2010 15:21:33 Lubos Lunak wrote:

Hello,

last IRC meeting we agreed on most new KDE repositories [*], I have updated http://en.opensuse.org/KDE/RepositoryRenaming with to match the setup we've agreed on and later I'll update the still pending issues (the unstable ones). However, since 11.3 is almost here, we should get KDE:Extra and KDE:UpdatedApps into shape.

I'll create a bugreport asking for updating the community repo list. I've also created http://en.opensuse.org/KDE/Extra_Repository and http://en.opensuse.org/KDE/UpdatedApps_Repository which should provide all information about the repos. Note that 'osc setlinkrev' currently seems to be broken, so KDE:UpdatedApps currently points to latest versions in KDE:Distro:Factory.

KDE:UpdatedApps should be now populated with everything from KDE:Distro:Factory that makes sense there, as already said setlinkrev doesn't work, but it could perhaps use some work to make some apps build on older distros, as feasible. There is a problem with defining what to do with build requirements. For example, Amarok requires taglib-extras, which requires taglib, which is provided in a sufficiently recent version only on 11.3, older repos don't build. Taglib-extras is more or less Amarok stuff, so including it there is fine. But taglib is a generic library not maintained by us, so it is a question if it is ok to include a newer version in KDE:UpdatedApps. One of the problems here is that since the repo is in the yast2 community list, potentionally a number of people can add it and end up with a version of the library that is not officially maintained on their distribution, and this might cause trouble (to the packager of it, and possibly even with the actual usage). Suggestions for how to handle such cases are welcome.

KDE:Extra is set up, but is currently almost empty. Feel free to copypac packages from KDE:KDE4:Community which make sense and will be maintained. If you want to maintain something in KDE:Extra (and do not want to maintain the repo as a whole), see http://en.opensuse.org/KDE/Extra_Repository for details (do submit requests or ask for maintainership for a specific package).

I've added maintainers to the repos for which I could find a record of them saying they'd want to become one, but I'm sure I missed several, so if you've said in the past you would help maintain the repo and you're not set up yes, just say here or on IRC.

[*] Which are actually called projects in osc and webui. Why do we call them repositories? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

On Monday 12 of July 2010, Markus Slopianka wrote:

I suggest to repurpose KDE:Community:

No. All of the repositories are intended to be community.

Since oS adopted a 8-months cycle we will frequently encounter skipped SC releases. Put into KDE:Community: UNSTABLE, community-supported point releases (like KDE SC 4.4.5), and community-supported major releases (SC 4.5).

That is not a matter of creating such repositories but somebody taking care of them. Will you be that somebody? -- 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

On Monday 12 July 2010 17:58:19 Lubos Lunak wrote:

That is not a matter of creating such repositories but somebody taking care of them. Will you be that somebody?

Cristian Morales Vega already offered to maintain a SC 4.5 repo. Dirk Müller has SC 4.4.5 in his home repo. Both could be just as well in "KDE:/Unsupported" (or whatever). Markus -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

On Monday 12 July 2010 15:21:33 Lubos Lunak wrote:

problem with defining what to do with build requirements. For example, Amarok requires taglib-extras, which requires taglib, which is provided in a sufficiently recent version only on 11.3, older repos don't build.

I think the rules should allow exception/update of specific cases after discussion of them on this list.

But taglib is a generic library not maintained by us, so it is a question if it is ok to include a newer version in KDE:UpdatedApps.

In the case of taglib I would agree to an update as it has afaik a proven record of backward compatibility/ I don't remember any problems with it ever. Bye, Steve -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

On Monday 12 July 2010, Lubos Lunak wrote:

[*] Which are actually called projects in osc and webui. Why do we call them repositories?

projects are a collection of source dirs (packages), repositories are a collection of binary packages. Therefore the usage of repositories is somewhat correct in the wiki imho. It could also be called project though, depending on how you view it. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org