Follow-up question: Given generic "tails" such as - gnome2/power-manager - gnome2/preferences - gnome2/print - gnome2/terminal
What happens down the road if and when, say, KDE gets more officially integrated into OpenSolaris? If a similar pattern is used, i.e. - kde4/power-manager - kde4/preferences - kde4/print - kde4/terminal and a user does a 'pkg install terminal', does the client then have to identify the conflict and present it to the user? (Not the end of the world if so, but in my mind it's another reason -- aside from familiarity for users -- to go with more unique, project-/executable-based names.) --joanie > 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. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
