Assuming I'm following all this correctly...
gnome2/speech/gnome2-speech
gnome2/accessibility/screen-reader
gnome2/accessibility/gnome-a11y-poke
would be installed via
# pkg install gnome2-speech
# pkg install screen-reader
# pkg install gnome-a11y-poke
respectively.(?)
If so, I'd suggest instead
gnome2/speech/gnome-speech
gnome2/accessibility/orca
gnome2/accessibility/accerciser
Glancing quickly over other items, it looks like 'terminal' was
similarly chosen instead of 'gnome-terminal' and 'calculator' over
'gcalctool'.
Personally, I think it would be great if (when feasible) package names
could correspond with actual (project and executable) names.
I tend to agree. In general, I think the final component should be the
familar name of the component so I'd prefer "orca" to "screen-reader".
Note this may result a certain lack of consistency in the names, a
attribute that's also clearly important with any bike-shedding
exercise. But I would put making the names expected/familar over make
them consistent.
An example I just realized which contradicts one of my comments to Rich
is SUNWlcms. I suggested putting it under library/liblcms since the
package does deliver a library by that name but as it also delivers a
set of commands. So perhaps a better name is library/lcms (which Rich
had) or even library/little-cms.
Looking at what other distributions use for particular FOSS cases isn't
a bad idea either.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
