On Friday 29 June 2007 11:55:11 pm Michael E Brown wrote:
What is a good way to handle this situation? Is there something that can be added to the next version to address this?
this is exactly what the development version of zypp/zypper does: duncan@piscolita:/space/build/zypper> sudo src/zypper sl # | Enabled | Refresh | Type | Name | URI --+---------+---------+--------+----------------------+----------------------------------------------------------------------- 1 | Yes | No | rpm-md | devel:tools:scm | http://software.opensuse.org/download/devel:/tools:/scm/openSUSE_10.2/ 1 | Yes | No | rpm-md | openSUSE_10.2_NonOSS | http://download.opensuse.org/distribution/10.2/repo/non-oss/suse 1 | Yes | No | rpm-md | openSUSE_10.2 | http://download.opensuse.org/distribution/10.2/repo/oss/suse 1 | Yes | No | rpm-md | KDE4_10.2 | http://software.opensuse.org/download/KDE:/KDE4/openSUSE_10.2 1 | Yes | No | rpm-md | homedmacvicar | http://software.opensuse.org/download/home:/dmacvicar/openSUSE_10.2/ duncan@piscolita:/space/build/zypper> ls /etc/zypp/repos.d/ devel:tools:scm.repo home:dmacvicar.repo KDE4_10.2.repo openSUSE_10.2_NonOSS.repo openSUSE_10.2.repo -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org