Age | Commit message (Collapse) | Author | Files | Lines |
|
make clean CLEANDEPENDS=YES
make deinstall DEINSTALLDEPENDS=YES
Both CLEANDEPENDS and DEINSTALLDEPENDS default to NO, so this isn't
different from the current behaviour.
|
|
for use, people better not use this).
|
|
from /var/db/pkg, but also from the pkgdb (in case someone does a
"make reinstall" with FORCE_PKG_REGISTER set). Pointed out by Greg Woods.
XXX This change is only effective if one has a pkg_* tools as of 19990302
or later, but I will not bump the PKGTOOLS_REQD version up, as I do
not expect many people to run into this (and if, it's not a problem).
One should just remove the check with ${_PKGTOOLS_VER} >= 19990302
if the version's bumped beyond 19990302.
|
|
|
|
This prevents that the pkg builder needs ${LOCALBASE/bin in $PATH.
Helps also with Peter Seebach's problem in PR 7047.
|
|
|
|
make(1) does not puke.
Add a note at the top of the file for people editing it, requesting them
to do just that.
|
|
|
|
|
|
If SPECIFIC_PKGS is defined (at the top-level of pkgsrc), then instead of
looping through all the categories and then all the packages within that,
simply loop through ${SITE_SPECIFIC_PKGS}, ${HOST_SPECIFIC_PKGS},
${GROUP_SPECIFIC_PKGS} and ${USER_SPECIFIC_PKGS}, which are whitespace
separated lists of categories/packages e.g.
SITE_SPECIFIC_PKGS+= devel/cvs security/ssh
The default behaviour is unchanged - if SPECIFIC_PKGS is not defined,
the whole hierarchy will be traversed.
Modify mk.conf.example to reflect the settings of SPECIFIC_PKGS,
SITE_SPECIFIC_PKGS, HOST_SPECIFIC_PKGS, GROUP_SPECIFIC_PKGS and
USER_SPECIFIC_PKGS.
Modify the ispell package to use the make definition ISPELL_LANG,
rather than just LANG (which can clash with the environment variable
of the same name), and modify mk.conf.example accordingly.
|
|
use "tar" for now.
|
|
be set there.
|
|
|
|
|
|
|
|
|
|
and "bsd.pkg.mk" will do the rest. Furthermore replace all remaining
instances of ":../../foo/bar" in dependences by ":${PKGSRCDIR}/foo/bar".
|
|
not in pkgsrc's info path, which confused me to no end.
|
|
base; install the symlink at ${LOCALBASE}/info/dir if there is nothing
there yet.
|
|
|
|
- do not depend on gtexinfo pkg even if USE_GTEXINFO is set
- if ${LOCALBASE}/info/dir is a regular file, nuke it and replace as a
symlink to /usr/share/info/dir. (Upgrades of the base system will
do this too, except that those will copy the contents of
/usr/pkg/info/dir first. There is no truly clean solution here.)
Also, use --info-dir=${LOCALBASE}/info/dir, NOT ${PREFIX}/info/dir.
info(1) only searches one directory file.
|
|
OBJECT_FMT, thanks to Thorsten Frueauf for finding this. (The error only
showed up if you defined UVM in mk.conf on a -current system)
|
|
pointed out by Alistair Crooks.
|
|
|
|
|
|
DTRT on ELF for e.g. lib/mozilla/*.
|
|
patch files, e.g. meta packages.
|
|
package into ${X11BASE}".
Replace all occurrences of BUILD_USES_X11 with USE_X11. This means "use X11
headers and libraries to build this package".
|
|
|
|
to avoid emulated instructions on the Motorola 68060 cpu.
|
|
and used to denote that a package uses X11 headers and libraries to
build, but does not install itself into X11BASE (xpkgwedge
notwithstanding).
This is used to ignore packages which would otherwise cause build
problems on machines with no X11 installation.
|
|
|
|
mawk and nawk can be used in bsd.pkg.mk (by setting AWK accordingly),
in PR pkg/6582. With thanks to Hubert for reminding me about this
one.
|
|
that the just installed package may be deinstalled with "make deinstall"
first.
Pointed out in PR 5973 by Kimmo Suominen <kim@tac.nyc.ny.us>.
|
|
Lines which start with tabs are shell commands. As we define no targets
in this file, they end up being unassosciated shell commands, and
cause make to bomb.
|
|
|
|
creates such with the `-release' (versus `-version-info') build option.
|
|
|
|
actually completed succesfully before continuing on with the current
build. This makes NOT_FOR_ARCHS and ONLY_FOR_ARCHS propogate up to
the pkgs which depend on them.
|
|
causes less confusion.
|
|
|
|
should exist in /var, not ${PREFIX}/var.
|
|
This can be used to
- enable execution of a non-standard target for all pkgs of a category,
e.g. cd pkgsrc/benchmarks ; make benchmark
- superceding standard-targets with custom versions, e.g. from
/etc/mk.conf
|
|
|
|
|
|
pointed out by Alistair Crooks and Johnny Lam.
|
|
/etc/mk.conf. Suggested by Johnny Chi-Lung Lam <jlbg+@andrew.cmu.edu>.
|
|
distribution site.
|
|
|
|
|