OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads Up: pkginfo.tmpl now supports architecture specific class action scripts

Date: Fri, 13 Apr 2007 11:34:43 +1000
From: Greg Price <Greg.Price at Sun dot COM>
To: on-all at Sun dot COM, onnv-gate at onnv dot sfbay dot sun dot com
Subject: Heads Up: pkginfo.tmpl now supports architecture specific class action scripts

With the putback of 6545198, usr/src/pkgdefs/bld_awk_pkginfo.ksh has 
been modified to allow the delivery of specified class action scripts to 
be restricted to the packages of specified architectures.

Previously, any class action script (in a CLASSES= directive) would be 
delivered to all architectures.

With this change, a CLASSES_arch= directive (where arch would normally 
be sparc or i386) can optionally be specified so specified class action 
scripts should only be included in the package for that architecture.

With the change comes two current restrictions:

1. classes should be surrounded by quotes. e.g. CLASSES="none foo bar"

2. architecture specific CLASSES_arch= should precede CLASSES= directives

e.g.

CLASSES_i386="foo"
CLASSES="none"

Cheers,
Greg