doc/packaging.txt
branchs11u3-sru
changeset 5632 4056b7992034
parent 3778 35735ffdda43
child 5633 94c600881baf
equal deleted inserted replaced
5631:01315954f757 5632:4056b7992034
   195       "$(PYV)" is that literal string, VERSION was the expanded value of
   195       "$(PYV)" is that literal string, VERSION was the expanded value of
   196       COMPONENT_VERSION from each component's Makefile (e.g., "0.6.0"
   196       COMPONENT_VERSION from each component's Makefile (e.g., "0.6.0"
   197       for alembic, "1.0.12" for amqp, etc.), and BUILD was set to
   197       for alembic, "1.0.12" for amqp, etc.), and BUILD was set to
   198       "5.12-5.12.0.0.0.41.0".  Note that BUILD needs to be set to
   198       "5.12-5.12.0.0.0.41.0".  Note that BUILD needs to be set to
   199       the value of the build you are integrating into.
   199       the value of the build you are integrating into.
   200     * one or more new manifests (typically one for the versionless package,
   200     * creation of the file "history" (or adding to it if it already exists)
   201       plus one for each versioned instance of the package) with actions:
   201       in each affected component directory; one or more new lines should be
   202       * set name=pkg.fmri value=pkg:/library/python-2/FOO@VERSION,BUILD
   202       added (typically one for the versionless package, plus one for each
   203       * set name=pkg.renamed value=true
   203       versioned instance of the package) with syntax:
   204       * set name=org.opensolaris.consolidation value=$(CONSOLIDATION)
   204       OLD-NAME@VERSION,BUILD NEW-NAME
   205       * depend fmri=library/python/FOO type=require
   205       for renames and:
   206       where FOO, VERSION and BUILD are all as above.
   206       OLD-NAME@VERSION,BUILD
       
   207       for obsoletions, where FOO, VERSION and BUILD are all as above.  Most
       
   208       Python modules, including the two mentioned above, have such files
       
   209       which can serve as examples.
   207 
   210 
   208     So far, not too bad.  This gets slightly more complicated when back-
   211     So far, not too bad.  This gets slightly more complicated when back-
   209     porting in that BUILD needs to be set to the back-port build (e.g.,
   212     porting in that BUILD needs to be set to the back-port build (e.g.,
   210     "5.11-0.175.3.0.0.8.0", as was the case for tkinter-27) rather than
   213     "5.11-0.175.3.0.0.8.0", as was the case for tkinter-27) rather than
   211     the S12 build.
   214     the S12 build.