Alvaro Lopez Ortega wrote: > Glynn Foster wrote: > >>> Since Ekiga is more popular now and it would be more definite and >>> accurate to tell users what product we deliver. And one more thing >>> is that SUNWgnome-meeting* have not been integrated into SNV, it >>> will not cause the compatibility issue. >> It's marked as 'Unstable' in the ekiga fasttrack, so I guess it >> makes it ok to change it [aside from the fact that we haven't >> shipped it previously]. >> >> In general though, we've gone for some pretty generic names for our >> package names, with some exceptions eg. evolution, realplayer, >> firefox, thunderbird. I don't think I have an opinion either way, so >> +1 from me providing existing installations can handle the upgrade. > > I don't agree.. we must be coherent with the package names. > > If the Gimp package is SUNWgnome-img-editor, Ekiga should be called > SUNWgnome-voip or something like that. > > I personally like to use generic names for the packages, in that > way, we won't suffer much if the community replace one of the > components of the stack (think of gnome-pdf and evince, for > instance). > I second Alo's objection. Last week we removed gnopernicus (SUNWgnome-a11y-reader) and put orca in its place. The package name is still SUNWgnome-a11y-reader.
As colourful and imaginative as community module names are, they frequently don't offer any obvious description of what the module delivers. "SUNWgnome-voip" is considerably more helpful than "SUNWekiga". Damien -- Damien Carbery, Gnome Release Engineer Ext: x (70) 19218
