Here's a small example (that's useful to me) that we can use to examine the review process, and to start to explore the consequences of the "tags and attributes" thread.
A tool I use occasionally, and would like to use more, is the Alloy Analyzer, from MIT's Software Design Group. It's an executable JAR file, so it's pretty easy to deliver, but requires a Java runtime. I don't think we closed on a software classification scheme, but one option is to use the freedesktop.org scheme that was mentioned. The package looks like $ pkg contents -m developer/alloy set name=fmri value=pkg://contrib/developer/[EMAIL PROTECTED],5.11-0:20080618T145524Z license 2cad8d32f2defa4b14b3ec1df11b43eda62943c7 license=alloy-mit pkg.size=1107 set name=description value="Alloy Analyzer" set name=pkg.summary value="Alloy Analyzer" set name=info.maintainer_url value=mailto:[EMAIL PROTECTED] set name=info.upstream_url value=http://alloy.mit.edu/alloy4/ set name=info.classification value=freedesktop.org:Development/IDE set name=authority value=contrib depend fmri=pkg:/[EMAIL PROTECTED] type=require dir group=sys mode=0755 owner=root path=usr dir group=bin mode=0755 owner=root path=usr/bin file d839d8d728d69e5c462140efa92109d5ddfb8e53 group=bin mode=0755 owner=root path=usr/bin/alloy4 pkg.size=3778077 Comments welcomed. - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
