From 707c77d465e50ab59169851144cbc80f38f16215 Mon Sep 17 00:00:00 2001 From: wiz Date: Sat, 9 Sep 2006 23:47:40 +0000 Subject: Document ALLFILES, reindent a bit. --- doc/guide/files/build.xml | 590 +++++++++++++++++++++++----------------------- 1 file changed, 297 insertions(+), 293 deletions(-) (limited to 'doc') diff --git a/doc/guide/files/build.xml b/doc/guide/files/build.xml index c23d73ab355..11b3ffed88c 100644 --- a/doc/guide/files/build.xml +++ b/doc/guide/files/build.xml @@ -1,211 +1,211 @@ - + -The build process - - -Introduction - -This chapter gives a detailed description on how a package is -built. Building a package is separated into different -phases (for example fetch, -build, install), all of which are -described in the following sections. Each phase is splitted into -so-called stages, which take the name of the -containing phase, prefixed by one of pre-, -do- or post-. (Examples are -pre-configure, post-build.) Most -of the actual work is done in the do-* stages. - -The basic steps for building a program are always the same. First -the program's source (distfile) must be brought to -the local system and then extracted. After any pkgsrc-specific patches -to compile properly are applied, the software can be configured, then -built (usually by compiling), and finally the generated binaries, etc. -can be put into place on the system. + The build process + + + Introduction + + This chapter gives a detailed description on how a package is + built. Building a package is separated into different + phases (for example fetch, + build, install), all of which are + described in the following sections. Each phase is splitted into + so-called stages, which take the name of the + containing phase, prefixed by one of pre-, + do- or post-. (Examples are + pre-configure, post-build.) Most + of the actual work is done in the do-* stages. + + The basic steps for building a program are always the same. First + the program's source (distfile) must be brought to + the local system and then extracted. After any pkgsrc-specific patches + to compile properly are applied, the software can be configured, then + built (usually by compiling), and finally the generated binaries, etc. + can be put into place on the system. - + Program location Before outlining the process performed by the &os; package system in - the next section, here's a brief discussion on where programs are - installed, and which variables influence this. + the next section, here's a brief discussion on where programs are + installed, and which variables influence this. The automatic variable PREFIX indicates - where all files of the final program shall be installed. It is - usually set to LOCALBASE - (/usr/pkg), or CROSSBASE - for pkgs in the cross category. The value of - PREFIX needs to be put - into the various places in the program's source where paths to - these files are encoded. See and for more details. + where all files of the final program shall be installed. It is + usually set to LOCALBASE + (/usr/pkg), or CROSSBASE + for pkgs in the cross category. The value of + PREFIX needs to be put + into the various places in the program's source where paths to + these files are encoded. See and for more details. When choosing which of these variables to use, - follow the following rules: + follow the following rules: PREFIX always points to the location where the current - pkg will be installed. When referring to a pkg's own installation path, - use ${PREFIX}. + pkg will be installed. When referring to a pkg's own installation path, + use ${PREFIX}. LOCALBASE is where all non-X11 pkgs are installed. - If you need to construct a -I or -L argument to the compiler to find - includes and libraries installed by another non-X11 pkg, use - ${LOCALBASE}. The name - LOCALBASE stems from FreeBSD, which - installed all packages in /usr/local. As - pkgsrc leaves /usr/local for the system - administrator, this variable is a misnomer. + If you need to construct a -I or -L argument to the compiler to find + includes and libraries installed by another non-X11 pkg, use + ${LOCALBASE}. The name + LOCALBASE stems from FreeBSD, which + installed all packages in /usr/local. As + pkgsrc leaves /usr/local for the system + administrator, this variable is a misnomer. X11BASE is where the actual X11 distribution (from - xsrc, etc.) is installed. When looking for - standard X11 includes (not - those installed by a pkg), use ${X11BASE}. + xsrc, etc.) is installed. When looking for + standard X11 includes (not + those installed by a pkg), use ${X11BASE}. X11-based packages are special in that they may be installed in - either X11BASE or LOCALBASE. + either X11BASE or LOCALBASE. Usually, X11 packages should be installed under - LOCALBASE whenever possible. Note that you will - need to include ../../mk/x11.buildlink3.mk - in them to request the - presence of X11 and to get the right compilation flags. + LOCALBASE whenever possible. Note that you will + need to include ../../mk/x11.buildlink3.mk + in them to request the + presence of X11 and to get the right compilation flags. Even though, there are some packages that cannot be installed - under LOCALBASE: those that come with app-defaults - files. These packages are special and they must be placed under - X11BASE. To accomplish this, set either - USE_X11BASE or USE_IMAKE in - your package. + under LOCALBASE: those that come with app-defaults + files. These packages are special and they must be placed under + X11BASE. To accomplish this, set either + USE_X11BASE or USE_IMAKE in + your package. Some notes: If you need - to find includes or libraries installed by a pkg that has - USE_IMAKE or USE_X11BASE in - its pkg Makefile, you need to look in - both ${X11BASE} and - ${LOCALBASE}. To force installation of - all X11 packages in LOCALBASE, the - pkgtools/xpkgwedge package - is enabled by default. + to find includes or libraries installed by a pkg that has + USE_IMAKE or USE_X11BASE in + its pkg Makefile, you need to look in + both ${X11BASE} and + ${LOCALBASE}. To force installation of + all X11 packages in LOCALBASE, the + pkgtools/xpkgwedge package + is enabled by default. X11PREFIX should be used to refer to the installed - location of an X11 package. X11PREFIX will be set to - X11BASE if xpkgwedge is not installed, - and to LOCALBASE if xpkgwedge is installed. + location of an X11 package. X11PREFIX will be set to + X11BASE if xpkgwedge is not installed, + and to LOCALBASE if xpkgwedge is installed. If xpkgwedge is installed, it is possible to have some packages installed - in X11BASE and some in LOCALBASE. - To determine the prefix of an installed package, the - EVAL_PREFIX definition can be used. It takes pairs in the - format DIRNAME=<package>, and the &man.make.1; variable - DIRNAME will be set to the prefix of the installed - package <package>, or ${X11PREFIX} if the package is - not installed. + in X11BASE and some in LOCALBASE. + To determine the prefix of an installed package, the + EVAL_PREFIX definition can be used. It takes pairs in the + format DIRNAME=<package>, and the &man.make.1; variable + DIRNAME will be set to the prefix of the installed + package <package>, or ${X11PREFIX} if the package is + not installed. This is best illustrated by example. The following lines are taken from - pkgsrc/wm/scwm/Makefile: + pkgsrc/wm/scwm/Makefile: - - EVAL_PREFIX+= GTKDIR=gtk+ - CONFIGURE_ARGS+= --with-guile-prefix=${LOCALBASE:Q} - CONFIGURE_ARGS+= --with-gtk-prefix=${GTKDIR:Q} - CONFIGURE_ARGS+= --enable-multibyte - + + EVAL_PREFIX+= GTKDIR=gtk+ + CONFIGURE_ARGS+= --with-guile-prefix=${LOCALBASE:Q} + CONFIGURE_ARGS+= --with-gtk-prefix=${GTKDIR:Q} + CONFIGURE_ARGS+= --enable-multibyte + Specific defaults can be defined for the packages evaluated using - EVAL_PREFIX, by using a definition of the form: + EVAL_PREFIX, by using a definition of the form: - - GTKDIR_DEFAULT= ${LOCALBASE} - + + GTKDIR_DEFAULT= ${LOCALBASE} + where GTKDIR corresponds - to the first definition in - the EVAL_PREFIX pair. + to the first definition in + the EVAL_PREFIX pair. - Within ${PREFIX}, packages should - install files according to &man.hier.7;, with the exception that - manual pages go into ${PREFIX}/man, not - ${PREFIX}/share/man. + Within ${PREFIX}, packages should + install files according to &man.hier.7;, with the exception that + manual pages go into ${PREFIX}/man, not + ${PREFIX}/share/man. - -Directories used during the build process - -When building a package, a number of directories is used to store -source files, temporary files, pkgsrc-internal files, and so on. These -directories are explained here. - -Some of the directory variables contain relative pathnames. There -are two common base directories for these relative directories: -PKGSRCDIR/PKGPATH is used for directories that are -pkgsrc-specific. WRKSRC is used for directories -inside the package itself. - - - -PKGSRCDIR -This is an absolute pathname that points to the pkgsrc -root directory. Generally, you don't need -it. - -PKGPATH -This is a pathname relative to -PKGSRCDIR that points to the current -package. - -WRKDIR -This is an absolute pathname pointing to the directory -where all work takes place. The distfiles are extraced to this -directory. It also contains temporary directories and log files used by -the various pkgsrc frameworks, like buildlink or -the wrappers. - -WRKSRC -This is an absolute pathname pointing to the directory -where the distfiles are extracted. It is usually a direct subdirectory -of WRKDIR, and often it's the only directory entry -that isn't hidden. This variable may be changed by a package -Makefile. - - - + + Directories used during the build process - -Running a phase + When building a package, a number of directories is used to store + source files, temporary files, pkgsrc-internal files, and so on. These + directories are explained here. -You can run a particular phase by typing make -phase, where phase is the name of the -phase. This will automatically run all phases that are required for this -phase. The default phase is build, that is, when you -run make without parameters in a package directory, -the package will be built, but not installed. + Some of the directory variables contain relative pathnames. There + are two common base directories for these relative directories: + PKGSRCDIR/PKGPATH is used for directories that are + pkgsrc-specific. WRKSRC is used for directories + inside the package itself. - + + + PKGSRCDIR + This is an absolute pathname that points to the pkgsrc + root directory. Generally, you don't need + it. + + PKGPATH + This is a pathname relative to + PKGSRCDIR that points to the current + package. + + WRKDIR + This is an absolute pathname pointing to the directory + where all work takes place. The distfiles are extraced to this + directory. It also contains temporary directories and log files used by + the various pkgsrc frameworks, like buildlink or + the wrappers. + + WRKSRC + This is an absolute pathname pointing to the directory + where the distfiles are extracted. It is usually a direct subdirectory + of WRKDIR, and often it's the only directory entry + that isn't hidden. This variable may be changed by a package + Makefile. + + + + + + Running a phase + + You can run a particular phase by typing make + phase, where phase is the name of the + phase. This will automatically run all phases that are required for this + phase. The default phase is build, that is, when you + run make without parameters in a package directory, + the package will be built, but not installed. + + - -The <emphasis>fetch</emphasis> phase + + The <emphasis>fetch</emphasis> phase The first step in building a package is to fetch the distribution files (distfiles) from the sites that are providing @@ -507,7 +507,7 @@ happens in the configure phase is roughly: .for d in ${CONFIGURE_DIRS} - cd ${WRKSRC} && cd ${d} && env ${CONFIGURE_ENV} \ + cd ${WRKSRC} && cd ${d} && env ${CONFIGURE_ENV} \ ${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS} .endfor @@ -538,7 +538,7 @@ is executed. .for d in ${BUILD_DIRS} - cd ${WRKSRC} && cd ${d} && env ${MAKE_ENV} \ + cd ${WRKSRC} && cd ${d} && env ${MAKE_ENV} \ ${MAKE_PROGRAM} ${BUILD_MAKE_FLAGS} \ -f ${MAKE_FILE} ${BUILD_TARGET} .endfor @@ -582,7 +582,7 @@ of MAKE_FILE is Makefile, and .for d in ${INSTALL_DIRS} - cd ${WRKSRC} && cd ${d} && env ${MAKE_ENV} \ + cd ${WRKSRC} && cd ${d} && env ${MAKE_ENV} \ ${MAKE_PROGRAM} ${INSTALL_MAKE_FLAGS} \ -f ${MAKE_FILE} ${BUILD_TARGET} .endfor @@ -651,14 +651,14 @@ of MAKE_FILE is Makefile, and - + - -The <emphasis>package</emphasis> phase + + The <emphasis>package</emphasis> phase -[TODO] + [TODO] - + Other helpful targets @@ -668,14 +668,14 @@ of MAKE_FILE is Makefile, and pre/post-* - For any of the main targets described in the previous section, two - auxiliary targets exist with pre- and - post- used as a prefix - for the main target's name. These targets are invoked before and - after the main target is called, allowing extra configuration or - installation steps be performed from a package's Makefile, for - example, which a program's configure script - or install target omitted. + For any of the main targets described in the previous + section, two auxiliary targets exist with + pre- and post- used as a + prefix for the main target's name. These targets are + invoked before and after the main target is called, allowing + extra configuration or installation steps be performed from + a package's Makefile, for example, which a program's + configure script or install target omitted. @@ -683,11 +683,12 @@ of MAKE_FILE is Makefile, and do-* - Should one of the main targets do the wrong thing, and should there - be no variable to fix this, you can redefine it with the do-* - target. (Note that redefining the target itself instead of the - do-* target is a bad idea, as the pre-* and post-* targets won't be - called anymore, etc.) You will not usually need to do this. + Should one of the main targets do the wrong thing, and + should there be no variable to fix this, you can redefine it + with the do-* target. (Note that redefining the target + itself instead of the do-* target is a bad idea, as the + pre-* and post-* targets won't be called anymore, etc.) You + will not usually need to do this. @@ -695,9 +696,10 @@ of MAKE_FILE is Makefile, and reinstall - If you did a make install and you noticed some file - was not installed properly, you can repeat the installation with this - target, which will ignore the already installed flag. + If you did a make install and you + noticed some file was not installed properly, you can repeat + the installation with this target, which will ignore the + already installed flag. @@ -706,8 +708,8 @@ of MAKE_FILE is Makefile, and This target does a &man.pkg.delete.1; in the current directory, - effectively de-installing the package. The following variables can - be used to tune the behaviour: + effectively de-installing the package. The following variables can + be used to tune the behaviour: @@ -723,11 +725,11 @@ of MAKE_FILE is Makefile, and Remove all packages that require (depend on) the given package. - This can be used to remove any packages that may have been pulled in - by a given package, e.g. if make deinstall - DEINSTALLDEPENDS=1 is done in - pkgsrc/x11/kde, this is likely to remove whole - KDE. Works by adding -R to the &man.pkg.delete.1; command line. + This can be used to remove any packages that may have been pulled in + by a given package, e.g. if make deinstall + DEINSTALLDEPENDS=1 is done in + pkgsrc/x11/kde, this is likely to remove whole + KDE. Works by adding -R to the &man.pkg.delete.1; command line. @@ -739,29 +741,29 @@ of MAKE_FILE is Makefile, and This target causes the current package to be updated to the latest - version. The package and all depending packages first get de-installed, - then current versions of the corresponding packages get compiled and - installed. This is similar to manually noting which packages are - currently installed, then performing a series of make - deinstall and make install (or whatever - UPDATE_TARGET is set to) for these packages. + version. The package and all depending packages first get de-installed, + then current versions of the corresponding packages get compiled and + installed. This is similar to manually noting which packages are + currently installed, then performing a series of make + deinstall and make install (or whatever + UPDATE_TARGET is set to) for these packages. You can use the update target to resume package - updating in case a previous make update was interrupted - for some reason. However, in this case, make sure you don't call - make clean or otherwise remove the list of dependent - packages in WRKDIR. Otherwise, you lose the - ability to automatically update the current package along with the - dependent packages you have installed. + updating in case a previous make update was interrupted + for some reason. However, in this case, make sure you don't call + make clean or otherwise remove the list of dependent + packages in WRKDIR. Otherwise, you lose the + ability to automatically update the current package along with the + dependent packages you have installed. Resuming an interrupted make update will only work as - long as the package tree remains unchanged. If the source code for - one of the packages to be updated has been changed, resuming - make update will most certainly fail! + long as the package tree remains unchanged. If the source code for + one of the packages to be updated has been changed, resuming + make update will most certainly fail! The following variables can be used either on the command line or in - /etc/mk.conf to alter the behaviour of - make update: + /etc/mk.conf to alter the behaviour of + make update: @@ -769,9 +771,9 @@ of MAKE_FILE is Makefile, and Install target to recursively use for the updated package and the - dependent packages. Defaults to DEPENDS_TARGET if set, - install otherwise for make update. - e.g. make update UPDATE_TARGET=package + dependent packages. Defaults to DEPENDS_TARGET if set, + install otherwise for make update. + e.g. make update UPDATE_TARGET=package @@ -780,11 +782,11 @@ of MAKE_FILE is Makefile, and Don't clean up after updating. Useful if you want to leave the - work sources of the updated packages around for inspection or - other purposes. Be sure you eventually clean up the source - tree (see the clean-update target below) or you may - run into troubles with old source code still lying around on your - next make or make update. + work sources of the updated packages around for inspection or + other purposes. Be sure you eventually clean up the source + tree (see the clean-update target below) or you may + run into troubles with old source code still lying around on your + next make or make update. @@ -793,9 +795,9 @@ of MAKE_FILE is Makefile, and Deinstall each package before installing (making - DEPENDS_TARGET). This may be necessary if the - clean-update target (see below) was called after - interrupting a running make update. + DEPENDS_TARGET). This may be necessary if the + clean-update target (see below) was called after + interrupting a running make update. @@ -804,12 +806,12 @@ of MAKE_FILE is Makefile, and Allows you to disable recursion and hardcode the target for - packages. The default is update for the update target, - facilitating a recursive update of prerequisite packages. - Only set DEPENDS_TARGET if you want to disable - recursive updates. Use UPDATE_TARGET instead to just - set a specific target for each package to be installed during - make update (see above). + packages. The default is update for the update target, + facilitating a recursive update of prerequisite packages. + Only set DEPENDS_TARGET if you want to disable + recursive updates. Use UPDATE_TARGET instead to just + set a specific target for each package to be installed during + make update (see above). @@ -821,29 +823,29 @@ of MAKE_FILE is Makefile, and Clean the source tree for all packages that would get updated if - make update was called from the current directory. - This target should not be used if the current package (or any of its - depending packages) have already been de-installed (e.g., after calling - make update) or you may lose some packages you intended - to update. As a rule of thumb: only use this target - before the first time you run - make update and only if you have a dirty package tree - (e.g., if you used NOCLEAN). + make update was called from the current directory. + This target should not be used if the current package (or any of its + depending packages) have already been de-installed (e.g., after calling + make update) or you may lose some packages you intended + to update. As a rule of thumb: only use this target + before the first time you run + make update and only if you have a dirty package tree + (e.g., if you used NOCLEAN). If you are unsure about whether your tree is clean, you can either - perform a make clean at the top of the tree, or use - the following sequence of commands from the directory of the package - you want to update (before running - make update for the first time, otherwise you lose - all the packages you wanted to update!): + perform a make clean at the top of the tree, or use + the following sequence of commands from the directory of the package + you want to update (before running + make update for the first time, otherwise you lose + all the packages you wanted to update!): # make clean-update -# make clean CLEANDEPENDS=YES -# make update + # make clean CLEANDEPENDS=YES + # make update The following variables can be used either on the command line or in - /etc/mk.conf to alter the behaviour of - make clean-update: + /etc/mk.conf to alter the behaviour of + make clean-update: @@ -851,11 +853,11 @@ of MAKE_FILE is Makefile, and After make clean, do not reconstruct the list of - directories to update for this package. Only use this if make - update successfully installed all packages you wanted to - update. Normally, this is done automatically on make - update, but may have been suppressed by the - NOCLEAN variable (see above). + directories to update for this package. Only use this if make + update successfully installed all packages you wanted to + update. Normally, this is done automatically on make + update, but may have been suppressed by the + NOCLEAN variable (see above). @@ -867,8 +869,8 @@ of MAKE_FILE is Makefile, and This target invokes &man.pkg.info.1; for the current - package. You can use this to check which version of a package is - installed. + package. You can use this to check which version of a package is + installed. @@ -900,11 +902,11 @@ of MAKE_FILE is Makefile, and Use this target to create a file README-all.html - which contains a list of all packages currently available in the &os; - Packages Collection, together with the category they belong to and a - short description. This file is compiled from the - pkgsrc/*/README.html files, so be sure to run - this after a make readme. + which contains a list of all packages currently available in the &os; + Packages Collection, together with the category they belong to and a + short description. This file is compiled from the + pkgsrc/*/README.html files, so be sure to run + this after a make readme. @@ -913,11 +915,11 @@ of MAKE_FILE is Makefile, and This is very much the same as the readme target (see - above), but is to be used when generating a pkgsrc tree to be written - to a CD-ROM. This target also produces - README.html files, and can be made to refer - to URLs based on CDROM_PKG_URL_HOST and - CDROM_PKG_URL_DIR. + above), but is to be used when generating a pkgsrc tree to be written + to a CD-ROM. This target also produces + README.html files, and can be made to refer + to URLs based on CDROM_PKG_URL_HOST and + CDROM_PKG_URL_DIR. @@ -925,9 +927,11 @@ of MAKE_FILE is Makefile, and show-distfiles - This target shows which distfiles and patchfiles are needed to build - the package. (DISTFILES and - PATCHFILES, but not patches/*) + This target shows which distfiles and patchfiles are + needed to build the package (ALLFILES, + which contains all DISTFILES and + PATCHFILES, but not + patches/*). @@ -936,10 +940,10 @@ of MAKE_FILE is Makefile, and This target shows nothing if the package is not installed. If a version - of this package is installed, but is not the version provided in this - version of pkgsrc, then a warning message is displayed. This target can - be used to show which of your installed packages are downlevel, and so - the old versions can be deleted, and the current ones added. + of this package is installed, but is not the version provided in this + version of pkgsrc, then a warning message is displayed. This target can + be used to show which of your installed packages are downlevel, and so + the old versions can be deleted, and the current ones added. @@ -948,11 +952,11 @@ of MAKE_FILE is Makefile, and This target shows the directory in the pkgsrc hierarchy from which the - package can be built and installed. This may not be the same directory - as the one from which the package was installed. This target is intended - to be used by people who may wish to upgrade many packages on a single - host, and can be invoked from the top-level pkgsrc Makefile by using the - show-host-specific-pkgs target. + package can be built and installed. This may not be the same directory + as the one from which the package was installed. This target is intended + to be used by people who may wish to upgrade many packages on a single + host, and can be invoked from the top-level pkgsrc Makefile by using the + show-host-specific-pkgs target. @@ -961,8 +965,8 @@ of MAKE_FILE is Makefile, and This target shows which installed packages match the current package's - DEPENDS. Useful if out of date dependencies are - causing build problems. + DEPENDS. Useful if out of date dependencies are + causing build problems. @@ -971,9 +975,9 @@ of MAKE_FILE is Makefile, and After a package is installed, check all its binaries and (on ELF - platforms) shared libraries to see if they find the shared libs they need. - Run by default if PKG_DEVELOPER is set in - /etc/mk.conf. + platforms) shared libraries to see if they find the shared libs they need. + Run by default if PKG_DEVELOPER is set in + /etc/mk.conf. @@ -982,25 +986,25 @@ of MAKE_FILE is Makefile, and After a make install from a new or - upgraded pkg, this prints out an attempt to generate a new - PLIST from a find -newer - work/.extract_done. An attempt is made to care - for shared libs etc., but it is - strongly recommended to review the - result before putting it into - PLIST. On upgrades, it's useful to - diff the output of this command against an already - existing PLIST file. + upgraded pkg, this prints out an attempt to generate a new + PLIST from a find -newer + work/.extract_done. An attempt is made to care + for shared libs etc., but it is + strongly recommended to review the + result before putting it into + PLIST. On upgrades, it's useful to + diff the output of this command against an already + existing PLIST file. If the package installs files via &man.tar.1; or other - methods that don't update file access times, be sure to - add these files manually to your - PLIST, as the find - -newer command used by this target won't catch - them! - - See for more - information on this target. + methods that don't update file access times, be sure to + add these files manually to your + PLIST, as the find + -newer command used by this target won't catch + them! + + See for more + information on this target. @@ -1009,15 +1013,15 @@ of MAKE_FILE is Makefile, and Used to do bulk builds. If an appropriate binary package already exists, - no action is taken. If not, this target will compile, install and - package it (and its depends, if PKG_DEPENDS is - set properly. See ). - After creating the binary - package, the sources, the just-installed package and its required - packages are removed, preserving free disk space. + no action is taken. If not, this target will compile, install and + package it (and its depends, if PKG_DEPENDS is + set properly. See ). + After creating the binary + package, the sources, the just-installed package and its required + packages are removed, preserving free disk space. Beware that this target may deinstall all - packages installed on a system! + packages installed on a system! @@ -1026,27 +1030,27 @@ of MAKE_FILE is Makefile, and Used during bulk-installs to install required packages. If an - up-to-date binary package is available, it will be installed via - &man.pkg.add.1;. If not, make bulk-package will be executed, - but the installed binary won't be removed. + up-to-date binary package is available, it will be installed via + &man.pkg.add.1;. If not, make bulk-package will be executed, + but the installed binary won't be removed. - A binary package is considered up-to-date to be - installed via &man.pkg.add.1; if: + A binary package is considered up-to-date to be + installed via &man.pkg.add.1; if: None of the package's files (Makefile, - ...) were modified since it was built. + ...) were modified since it was built. None of the package's required (binary) packages were - modified since it was built. + modified since it was built. Beware that this target may deinstall all - packages installed on a system! + packages installed on a system! -- cgit v1.2.3