Lines Matching full:be

19 .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT,
74 Some core modules are a single word, all other modules should be
94 a module will be global to the ports framework, and thus may interfere
99 should be named
106 internal variables and targets not intended for user consumption should be
112 For instance, if a module wants some value to be available for the rest
131 variables will usually drop the version suffix and be simply called
133 so that a port using the module can be switched from version to version
156 to be needed were added.
157 If several modules define the same hook, hook behaviors will be
163 hook that can be activated by defining
165 It will be run right after
170 hook that can be activated by defining
172 It will be run right after
177 hook that can be activated by defining
179 It will be run right after
187 hook that can be activated by defining
189 It will be run right after
219 hook that can be activated by defining
221 This will be invoked right after
227 This can occasionally be used for ports that require some specific
228 fake installation setup that will be provided by runtime dependencies.
232 hook that can be activated by defining
234 This will be invoked at the end of
245 can't be overridden simply.
278 Some variables can be overridden by modules.
289 The following variables can be overridden in a relatively safe fashion:
319 The following variables can be added to in a relatively safe fashion:
340 Some modules correspond to extra ports that will be used mostly as
358 to select specific behavior: build-time dependencies will always be
360 Runtime dependencies will be selected on a subpackage basis,
378 Thus they can be affected by user choices such as setting a variable
446 is set, the following variables will be set.
451 will be set to the standard installation directory for
458 should be used as such:
471 If this target isn't defined, it will be added automatically.
473 The actual test command to be run could be specified in the
483 Any local user will be able to connect without password.
487 variable is set, the database with such name will be set up before
507 respectively; those argument lists could be used in test scripts
516 If this target isn't defined, it will be added automatically.
518 The actual test command to be run could be specified in the
526 The path to directory where socket will be created is set by
530 Any local user will be able to connect without password.
534 variable is set, the database with such name will be set up before
572 Should not be used in ports Makefiles.
577 Should not be used in ports Makefiles.
615 will be put at the front of the
630 where schemas files will be installed.
661 Should not be used in ports Makefiles.
682 targets that can be overridden in the port Makefile.
698 should be set to the name of the font family.
714 they will be installed to
718 will be installed, with a fallback to ttf.
723 they will be installed to
743 then the gcc4 compilers will be put at the front of the path.
745 If other languages are needed, they must be listed in
750 variable can be used to change the version of gcc.
804 If architecture is in MODCLANG_ARCHS, the Clang compilers will be
807 If other languages are needed, they must be listed in
861 Ports can be built with several lua versions.
952 This can be added to
993 Ports using Rust must use this module so a rebuild can be triggered via
998 as appropriate for the architecture so it can be added to
1019 is the default version used by all Tcl ports and may be overridden.
1037 will be put at the front of the path.
1121 will be run during
1203 module should be used instead of using
1220 Qt5 and Qt6 consist of many so called Qt modules, these Qt modules should be
1241 may be overridden.
1280 Xfce ports can be divided into five categories: core libraries and
1297 One of the latter has to be provided by the port Makefile.