as it's only used internally by bsd.prefs.mk.
* Make _PKGSRCDIR a public variable by renaming it to PKGSRCDIR.
Also, generate its value from ${_PKGSRC_TOPDIR} so it's less fragile
than the old method of stripping off the last two components of
${.CURDIR}. PKGSRCDIR may now be used after bsd.prefs.mk is defined.
* Change all references to _PKGSRCDIR to PKGSRCDIR.
don't descend into this directory for anything since these packages aren't
packages in the normal sense, since they're not expected to install or
package correctly.
List all packages that depend on a particular package; needs the INDEX file
Usage: 'make show-deps PKG=openssl'
PKG: name of the package
No make dependency on INDEX by purpose, since INDEX generation
right now happens too often (too much phoniness, I guess).
several orders of magnitude and 'make index' now takes 30 minutes or so
instead of several days on my test machine. The approach now is to take
one pass through every package and extract some key information including
the explicitly listed dependencies. After the data is extracted, the
dependencies are flattened in one step which avoids the extremely
inefficient recursive make that was previously used.
new and much more efficient code. Previously a 'make readme' took over
3 weeks on my SS5 and now takes < 3 hours. The number of make calls has
been reduced from somewhere over 1,000,000 to one per package which is
around 3,000. The mk/scripts/mkreadme script does all the work now. This
script has been used in standalone form for a month or two on ftp.netbsd.org
and has had no problem.
Otherwise a bad value of _PKGSRCDIR will be used and the bulk cache creation
fails. This didn't show up before because formerly _PKGSRCDIR was previously
set in bsd.pkg.mk instead of bsd.prefs.mk as it is now.
Should fix bulk build dependency problems noted recently by Hubert.
the cache files used during a bulk pkgsrc build.
- replace the code in the build script that used to create the cache
files with a 'make bulk-cache' call.
sets MKCRYPTO=no, packages in this category won't be fetched, installed,
built, or packaged. Also, binary package users forbidden, by law, from
using strong cryptography would presumably find the list on the category's
automatically generated web page useful for ensuring compliance.
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.
