On 2013-03-30 10:00 (GMT+0100) Wolfgang Rosenauer composed:

Felix Miata composed:

...

[12.1] zypper rm MozillaFirefox wants to install MozillaThunderbird

...

Anyone know why?

No, I do not see any reason for it. Do you have any more details from the output.

I don't think so, at least, there was nothing that I can remember. I did forget to mention at the OP time that the DE was KDE, and that seamonkey was installed, if that might have made any difference to some package that depends on a Mozilla browser being installed rather than Konq being sufficient.

...

Anyone know why these packages use caps, or prepend Mozilla to the actual program name? Fedora doesn't. Mageia doesn't. No other distro I can remember does it. All distros providing them, except for openSUSE, AFAIK are content with packages named firefox and thunderbird.

openSUSE/SUSE shipping those for ages and I've never seen a reason to change the name for the sake of changing a name.

IIRC when Firefox still was named Firebird it was basically needed to call it MozillaFirebird (or mozilla-firebird but I've chosen MozillaFirebird). When it was renamed to Firefox I changed the package to MozillaFirefox in February 2004 and kept it because of what I wrote above. What is your exact issue with that?

e.g., try to discover its installed version without running X: # rpm -qa | grep firefox # Grepping for irefox is workaround, but that's not intuitive to everyone. e.g., goto "f"s in a mirror's FTP listing to see what versions are on the host. Oops, nothing there, as FTP listings are case sensitive, and the random selection of package names starting with a cap are listed first. Same goes in /usr/share/applications/, whereas everywhere else in /usr/ *irefox is all lower case. YaST2 also sorts case sensitively. Then there's the original Mozilla Suite product's evolutionary result, Netscape->Mozilla->SeaMonkey, spelled without any caps everywhere in the package and file systems. So within openSUSE, some Mozilla packages use caps, while others don't. Some of this stems from seeing messages about zypper up not going to upgrade MozillaFirefox and wanting to figure out why, which typically has to do with whether or not only standard repos are enabled, or whether any Mozilla repo is also enabled, where the currently installed version came from, and wondering why when version a.b.c is the installed version right after updating while on Mozilla's download mirrors version a.b.d has been out for multiple weeks. I'd like to see the all the caps gone from all package names for 13.1.

You can still do "zypper in firefox" or "zypper in thunderbird".

It is not intuitive that one can install a package without using its actual name in an environment where trying to add or remove a kernel without typing its inexplicable intermixing of numerals, dots and dashes just right is always an exercise in frustration. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Wolfgang Rosenauer 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. 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. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, Mar 30, 2013 at 01:53:30PM +0100, Wolfgang Rosenauer wrote:

Am 30.03.2013 13:50, schrieb Greg Freemyer:

...

Wolfgang Rosenauer 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