On Thursday, November 24, 2011 09:58:41 todd rme wrote:
On Wed, Nov 23, 2011 at 11:03 PM, Jos Poortvliet <jos@opensuse.org> wrote:
Heya all,
Going back to the discussion we had a while ago about moving to Tumbleweed in openSUSE 12.1.
After a little bit of thinking* I concluded that of course all (new) tumbleweed users need to move over to this setup of using the 'current' instead of the 12.1 repositories. So I changed the Tumbleweed page to reflect this: http://en.opensuse.org/Portal:Tumbleweed And also: http://en.opensuse.org/SDB:Change_from_12.1_to_Tumbleweed
It makes the text a bit complicated. And I suck at un-complicating it, I suppose, help is welcome.
But there is another matter I'm sure some of you object to much more strongly: I use a self-made one-click-install file for adding Tumbleweed**. I dunno if OCI can remove repo's but at least I can add the right ones... However. I have no idea where to host the file. So for now I put it on my *anathema* public dropbox...
/me hides
Yes, horrible, I know. I'm however sure our sysadmins can find a much better spot for this one-click install. And maybe also for the one-click-install for ownCloud, if we have one that works better?!? http://en.opensuse.org/Portal:Tumbleweed
I just decided to go ahead, make the OCI and put it somewhere to have at least an improvement over the current situation ;-)
The openSUSE-KDE team hosts them inside their own repo. For instance take a look here:
http://download.opensuse.org/repositories/KDE:/Distro:/Factory/openSUSE_12.1 /
You can see they have KDE4-BASIS.ymp, KDE4-DEFAULT.ymp, KDE4-DEVEL.ymp, and KDE4-GAMES.ymp hosted right in their repo directory tree. That seems like a logical place for it, especially since anyone trying to set it up manually will automatically come across the ymp files when doing so. You could probably ask them how they do that.
Now THIS is an excellent suggestion. I think I'll try to create a 'package' with just that file, then submit it to Tumbleweed so it can be maintained in there :D See if GregKH likes that idea... Meanwhile, I understood OCI can not help us remove the 'old' repositories. I have written down in the how-to on openSUSE.org/Tumbleweed how to remove them but it'd be far nicer if OCI could take care of that. I suspect giving OCI such power is a bit dangerous from a security perspective? Or is it something we could add some day, provided someone steps up to do it?
-Todd