Hi,
There's a feature in libzypp that we'd like to use to make it easier for people to use the GNOME:STABLE repositories. This is RIS: http://old-en.opensuse.org/Standards/Repository_Index_Service
I played a bit with it, and it's all working fine. Except that there's this behavior: "Newly added repositories should be added as disabled."
So we tell people to run "zypper as <url> <alias> && zypper refs", but it's not enough, and we have to tell them to manually enable the repos created by the service. It could be argued that it's not that much of an issue, but if we change the RIS index, then new repos have to be manually enabled again.
Is there any way to make this just work? Or do other people using RIS have a suggestion to improve the workflow for the user?
Note that I do understand that for security, we'd want the repos to be disabled by default. But, well, it kind of makes RIS less useful :/
Thanks,
Vincent
Hi,
I also took a look at RIS some time ago...
On 16/09/10 16:57, Vincent Untz wrote:
I played a bit with it, and it's all working fine. Except that there's this behavior: "Newly added repositories should be added as disabled."
And also thought that this is really stupid :-(
Note that I do understand that for security, we'd want the repos to be disabled by default. But, well, it kind of makes RIS less useful :/
I see two use cases for RIS:
1. Public RIS for standard repos. Here it is IMHO OK to add them disabled, if there would be a GUI to enable them later on. Or maybe enable the required repos as part of adding RIS.
2. Private/Corporate/System-wide RIS. Here one usually wants to set a policy centrally and have the clients "do what I told you to". Here it would be really important to have the abilitiy to enable and disable repos through RIS itself, e.g. by adding an attribute to the Repo XML that sets the repo to be enabled or not.
Here it is also important that any "zypper refs" will en/disable repos accordingly to what RIS says!
This way we could get a cheapomatic yum channel manager (the RIS XML could be created by a script with per-host customization ...) without much effort on the zypper side and without impairing anything to the regular user.
Maybe we should open a FATE for this?
Kind Regards, Schlomo
-
Schlomo Schapiro -
Vincent Untz