I have some questions regarding repository setup for zypp. I know the "zypper service-add ..." stuff, and I currently have the Dell public repositories bootstrap script use this in the script. I was looking to improve this, though. For yum setup, the setup is simply this: drop a "dell.repo" file in /etc/yum.repos.d/. This is quite nice for the simple reason that it is something that RPM manages to do exceedingly well. I have a "dell-unsupported-repository-1-1.noarch.rpm" that I use for this purpose. The other nice thing about this is that I can very easily manage the transition from config to config. For example, if I make a change to the repository layout, I can release updated repository RPMs with the new configs. As I normally will make the old and new layouts compatible, I can simply wait a period of time before removing the backwards compatibility (either symlinks or http redirects, etc). This makes things nice and easy to manage from my side. For zypper, I dont see a nice way to update the client's configs easily via RPM. I tried to do the "zypper service-add ..." inside the RPM %post, but all I managed to do was hang zypper when the RPM was updated as part of a zypper upgrade. What is a good way to handle this situation? Is there something that can be added to the next version to address this? Note: All my testing was carried on on SLES10 and SLES10 SP1. Thanks, Michael Brown Maintainer, Dell unofficial yum repos Dell, Inc -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org