On Sat, Mar 30, 2013 at 01:53:30PM +0100, Wolfgang Rosenauer wrote:
Am 30.03.2013 13:50, schrieb Greg Freemyer:
Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
If someone contributes some smart changes together with a workflow to keep my work the same and change the package name at some point I'm all in to hear about that. If changing a package name in released openSUSE versions is fine for everybody and risk free (do not think it really is) then it might be possible to switch as well.
Wolfgang
I've done renames of a heavily "buildrequires" package that went to factory with no problem. I don't know why it wouldn't be risk free in the update repo.
Factory is not the issue at least.
I guess you know you just put something like this in the new specfile.:
Provides: MozillaFirefox-%version Obsoletes: MozillaFirefox < 20.0.0
Where 20.0.0 is the version you first release under the new name.
You never know which (probably broken) package/software relies on the fact that Firefox is called MozillaFirefox in some released distribution for example. I usually try to avoid such risks as good as possible.
Yes, please do not rename the package in released distributions ... Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org