Bart Smaalders wrote:
Chris Quenelle wrote:
Bart,

Sounds good!

-- Where do I get UI buy-in for packages showing up in multiple categories? I assume any UI review process
   would be driven by the engineers working on PM, so
   first should I file an RFE for PM, and get buy-in from
   the engineering team?  Or is there someplace else I    should start?


You should start that discussion on this list.
When doing the UI design we initially considered placing packages in multiple categories but decided not to. The reason was to keep the number of categories/subcategories to a reasonable minimum. The longer the list of categories the harder it is to find a likely candidate category. In the end it is a balancing act between the number of categories and the number of entries in a category.

Your concerns can be addressed via search. While SunStudioExpress is categorized under "Integrated Development Environment", you can search for "C++" and see both SunStudioExpress and Netbeans. This is dependent on the packages having good descriptions, but this isn't really any different than insuring a package would be categorized into all the appropriate categories. And packages should still have good descriptions.

Frank

-- Looking ahead, if this was approved, do we know how to
   set up the meta-data in the packages for multiple
   categories?   Can the same attribute appear more than once?


A single set attribute can have multiple values.

The page at [1] lists gui.classification, but not info.classification.
And it doesn't describe the syntax for the value.
Is there an up-to-date spec someplace of the latest and greatest set?
(Like a source file with comments or something like that?)

What does this part of the value mean?
     org.opensolaris.category.2008


This was discussed fairly extensively in this list...

See http://defect.opensolaris.org/bz/show_bug.cgi?id=4100




_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to