| | |
| | | automatically. It is defined in $(WS_MAKE_RULES)/environment.mk which is |
| | | included by $(WS_MAKE_RULES)/shares-macros.mk. It uses the REQUIRE_PACKAGES |
| | | macro contents to attempt to install any required packages in the current |
| | | environment. It should never by used by developers to update any public |
| | | build machines as those are managed by dedicated staff. To use this target |
| | | user has to be assigned "Software Installation" or "Primary Administrator" |
| | | profile. |
| | | environment. To use this target user has to be assigned "Software Installation" |
| | | or "Primary Administrator" profile. |
| | | |
| | | download:: |
| | | This target is present in all Makefiles. It can be used at the top level |
| | |
| | | by the inclusion of $(WS_MAKE_RULES)/prep.mk. It will run the build steps |
| | | necessary to pkglint the manifests for a component. |
| | | |
| | | publish:: |
| | | pre-publish:: |
| | | This target is present in all Makefiles. It can be used at the top level |
| | | to act across all components, or on an individual component basis. It is |
| | | automatically defined by including $(WS_MAKE_RULES)/ips.mk. It depends |
| | | on the previously described 'install' target and will perform a series of |
| | | internal, intermediate steps to use the component package manifests to |
| | | generate and publish packages for that component. |
| | | generate and validate consistency of packages for that component. |
| | | |
| | | NOTE: The pre-publish target aims to help a recipe developer to make sure |
| | | that the recipe can produce a valid package without actually pushing its |
| | | bits into his or her repository (allows to experiment, saves some time, and |
| | | avoids polluting the repository with known-bad code during development cycles). |
| | | |
| | | publish:: |
| | | This target is present in all Makefiles. It can be used at the top level |
| | | to act across all components, or on an individual component basis. It is |
| | | automatically defined by including $(WS_MAKE_RULES)/ips.mk. It depends |
| | | on the previously described 'pre-publish' target and will actually publish |
| | | packages for that component to the repository configured in $(WS_REPO). |
| | | |
| | | clean:: |
| | | This target is present in all Makefiles. It can be used at the top level |
| | |
| | | print-VAR |
| | | This target will print contents of variable VAR and also provide information |
| | | about variable origin and variable flavor. |
| | | |
| | | print-value-VAR |
| | | This target will print contents of variable VAR. |
| | | |
| | | format |
| | | This target will apply different refactoring rules to update the Makefile |
| | | to the current style: deprecation of macros, use of new target, autoindent... |
| | | The rules are implemented in the userland-component utility. |
| | | |
| | | update |
| | | This target will format the Makefile then bump the COMPONENT_REVISION variable |
| | | if no VERSION value is provided. If a VERSION value is provided it will set |
| | | the COMPONENT_VERSION to the given value and remove COMPONENT_REVISION. |
| | | For some supported build style it may peform additional actions like: |
| | | - infering the latest version if VERSION=latest is passed, |
| | | - updating the archive checksum. |
| | | |
| | | update-latest |
| | | This target is a convenience shortcut for 'update VERSION=latest'. |