Michael Honeyfield wrote:
the addition of a Provides: suse-release and a Obsoletes: suse-release will fix issues around a naming convention with packages.. its a non-event and a pointless arguement still...
Well okay, look at it this way: I'm a newbie to Linux so don't know how the different packages are capitalized. Linux is sensitive to capitalization, so won't it give an error when I try to execute the package SuSEfirewall2-3.3-18.2 by typing susefirewall2-3.3-18.2? At least if one standard convention were enforced, then one wouldn't have to worry about such things, and the broken scripts that houghi spoke of:
I am sure they have better things to do then rename all programs from SuSE* to SUSE* or suse* or whatever and then have the problems of scripts that won't run anymore.
Sure they have better (and more important) things to do than rename, which means I agree it's not as big a priority as many other things, but I'd like to point out that the priority should not exactly be low, either. [Besides how much difficulty is it going to be to tell the computer to search for all occurrences of filereferences with one capitalization and replace it with another capitalization?] Would you like it if one Linux maker had Gcc and another had gCC and another had gcc and another GCC? Because it's universally gcc, you and I have no problem running different flavours of Linux, and yet getting the same results. And documentation on the net or anywhere which tells the user to enter the word gcc becomes universal. Else they would have to add something like: "please check with your distro provider for the exact capitalization of gcc because Linux is case-sensitive and using a wrong capitalization will probably just give you an error 'no such file or directory'". Would you like that? I say that this problem of different capitalizations should have been cut out at the start, but now that it has been allowed to grow to a certain extent, it should not be allowed to proliferate anymore, a single capitalization being officially determined by Novell, and used thence *everywhere*. Or at least some official guideline that says: "The product name is SUSE, but in all packages, all small letters must be used as in susefirewall." Of course, such an official announcement will not prevent users from casually referring to their system as a Suse box or (from the olden days) a SuSE box. But when it comes to official stuff, which affects what kind of commands we enter, I think some guideline must be announced/recommended. After that, I stop starting/continuing threads like this which would *then* (but not now) be pointless. -- Shriramana Sharma http://samvit.org