Hey all, I have a YaST product that is being renamed, but we would like to preserve a smooth upgrade path for existing users. Ideally, I would like customers to be able to use "Patch-CD Update" on our new product, and have the following happen: - Old product is automatically removed. Any packages completely unique to the old product are also removed. - New product is installed, and the associated pattern is automatically selected. - Any RPM's that are common between the two products are updated Bonus: - Services automatically updated. Activation codes for the old product services will still be valid with the new product's services and I would like to make the services update as smooth as possible. Currently, I have the new product configured, and it works well for new installations, but the update path is incomplete. I tried adding a "weakremove" line into the new product's release package spec file referring to the old product's release package, but that did not seem to work, as the old product's release package is not automatically removed during the new product's install. What is the best way to perform a product name change while preserving a smooth update path? Here is the short discussion I originally started on the buildservice mailing list: http://lists.opensuse.org/opensuse-buildservice/2013-05/msg00171.html As always, thank you for your help. ~Nathan Cooper -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org