this variable, since, as of revision 1.1404 of mk/bsd.pkg.mk,
LIBTOOL_OVERRIDE is set to "libtool */libtool */*/libtool", which will
suffice in most cases.
Change step 3 in section 10.38 to indicate that "share/omf" _should_ be
removed from PLIST (previously it said to not remove it).
XML_CATALOGS should hold XML catalogs, not SGML.
fine-grained distinction between required versions of pre-requisites
(DEPENDS) and versions that are recommended for security or library ABI
consistency reasons (RECOMMENDED).
The contents of ${RECOMMENDED} are added to DEPENDS unless
IGNORE_RECOMMENDED is set to YES, in which case a warning will be printed
and IGNORE_RECOMMENDED will be added to BUILD_DEFS.
Add a corresponding BUILDLINK_RECOMMENDED.<pkg> variable for use with
buildlink2 and buildlink3.
Remove redundant paragraphs, and remind creating a user account if
$CVS_USER is set in build.conf. (We should probably check for a few
things there...)
makeinfo commands.
The goal of the new framework is twofold:
- reduce the number of '@exec' and '@unexec' in PLIST by
using INSTALL/DEINSTALL scripts to handle entries addition/removal
Info directory file.
- achieve lighter dependencies by avoiding unnecessary run-time
dependency on the gtexinfo package and if needed with the help of the
standalone install-info command provided by the recently imported package
pkgtools/pkg_install-info.
A package must be sightly updated to use this new framework and
must define the variable USE_NEW_TEXINFO. This variable will
be removed from the pkgsrc tree when all package would have been
updated.
For details see section 10.24 of Packages.txt, comments in
mk/{texinfo.mk,buildlink2/bsd.buildlink2.mk} and upcoming mail to
<tech-pkg at netbsd dot org>.
archives for better tracking and archiving:
11.1 Submitting your packages
=============================
...
* packages:
First, check that your package is complete, compiles and runs well; see
section 9 and the rest of this document. Next, generate an uuencoded
gzipped tar(1) archive, preferably with all files in a single directory.
Finally, send-pr(1) with category "pkg", a synopsis which includes the
package name and version number, a short description of your package
(contents of the COMMENT variable or DESCR file are OK) and attach the
archive to your PR.
If you want to submit several packages, please send a separate PR for
each one, it's easier for us to track things that way.
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
