doc/packaging.txt
changeset 4813 5e86eaf216ff
parent 3817 30b42c38bbc4
child 5072 3f6521b6cb16
equal deleted inserted replaced
4812:874a021a99a5 4813:5e86eaf216ff
   185       "$(PYV)" is that literal string, VERSION was the expanded value of
   185       "$(PYV)" is that literal string, VERSION was the expanded value of
   186       COMPONENT_VERSION from each component's Makefile (e.g., "0.6.0"
   186       COMPONENT_VERSION from each component's Makefile (e.g., "0.6.0"
   187       for alembic, "1.0.12" for amqp, etc.), and BUILD was set to
   187       for alembic, "1.0.12" for amqp, etc.), and BUILD was set to
   188       "5.12-5.12.0.0.0.41.0".  Note that BUILD needs to be set to
   188       "5.12-5.12.0.0.0.41.0".  Note that BUILD needs to be set to
   189       the value of the build you are integrating into.
   189       the value of the build you are integrating into.
   190     * one or more new manifests (typically one for the versionless package,
   190     * creation of the file "history" (or adding to it if it already exists)
   191       plus one for each versioned instance of the package) with actions:
   191       in each affected component directory; one or more new lines should be
   192       * set name=pkg.fmri value=pkg:/library/python-2/FOO@VERSION,BUILD
   192       added (typically one for the versionless package, plus one for each
   193       * set name=pkg.renamed value=true
   193       versioned instance of the package) with syntax:
   194       * set name=org.opensolaris.consolidation value=$(CONSOLIDATION)
   194       OLD-NAME@VERSION,BUILD NEW-NAME
   195       * depend fmri=library/python/FOO type=require
   195       for renames and:
   196       where FOO, VERSION and BUILD are all as above.
   196       OLD-NAME@VERSION,BUILD
       
   197       for obsoletions, where FOO, VERSION and BUILD are all as above.  Most
       
   198       Python modules, including the two mentioned above, have such files
       
   199       which can serve as examples.
   197 
   200 
   198     So far, not too bad.  This gets slightly more complicated when back-
   201     So far, not too bad.  This gets slightly more complicated when back-
   199     porting in that BUILD needs to be set to the back-port build (e.g.,
   202     porting in that BUILD needs to be set to the back-port build (e.g.,
   200     "5.11-0.175.3.0.0.8.0", as was the case for tkinter-27) rather than
   203     "5.11-0.175.3.0.0.8.0", as was the case for tkinter-27) rather than
   201     the S12 build.
   204     the S12 build.