Shawn Walker wrote: > On 01/ 7/10 01:19 AM, John Rice wrote: >> The only sensible way to do this with the current scheme is to make sure >> that the first categorization metadata in info.classification (allows >> for multiple classifications) matches the first portion of the hierarchy >> name for that package. If it does we can strip it when displaying the >> name if the user has clicked on a specific category. > > I don't think you can assume that the info.classification has any > relation to the package namespace whatsoever. In particular, the > package names can't contain spaces, but the info.classification can. >
The category hierarchy in the GUI (called "classification") and the category hierarchy in the new package name (henceforth called "package name hierarchy element" (PNHE)) NEED to be reconciled in some sensible fashion or the introduction of PNHEs will cause the PM GUI to become cluttered and confusing. IMHO A larger problem than PM GUI usability is the confusion that will result when users try to discuss packages. One set of users (cmd line) will be certain that the grep package is in the "utility" category and the other set (gui users) will be certain it's in the "system" category. They won't realize they're talking different languages until after exchanging a few emails. Upon resolving their confusion, they will ask "why did Sun set it up this way?" If we move towards using project names for the base package names, then the GUI could normally show only the base name if it's globally unique. If non-unique cases are rare, then the GUI could use a heuristic for disambiguation. --chris _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
