In appendix A, the word pkglint is meant as a utility name, not
necessarily the command. This change removes the bold formatting from the
toc, where it looked too unusual.
These patches would be much harder to edit and read than ordinary files.
Also recommend to copy these files in post-extract instead of
pre-configure, since extract is used for putting all files in place.
The bison example package is quite old-fashioned, therefore the modern
pkglint generates quite a few warnings for it. These also serve better in
the example than a mere "looks fine".
This option was kind of useful when the -Cextra option still existed (up
to 2019-02-19). After that date, it only enabled checks for the pkgsrc
infrastructure files, inter-package checks, as well as other checks on
files unrelated to the current package. These checks tend to be more
confusing than being helpful when checking a single package. They are
still useful when checking the whole pkgsrc tree at once, but that's a
special case.
This keeps the font size on mobile devices more consistent by splitting
long preformatted lines.
Also, replace some http URLs with their https counterparts.
This example makes it easier to see that the assignment operator should
always be += instead of a simple =. Also remove the word dewey since that
is a classification scheme for libraries, not a versioning scheme.
TeXlive packages are unusual in avoiding direct downloads from the upstream
CTAN repository. Therefore, developers must manually upload the appropriate
distfiles. To help avoid forgetting this step, add a description to the
Pkgsrc Guide in the section describing TeXlive packages.
For more than 15 years, pkglint complains about relative directories that
take shortcuts. All relative paths between packages should first go up to
the pkgsrc root and from there to the package.
Document TOOL_DEPENDS and clarify the differencies with BUILD_DEPENDS.
Adjust previous BUILD_DEPENDS examples (all of them were actually
TOOL_DEPENDS).
XXX: No BUILD_DEPENDS example is provided, if you have any good and common
XXX: BUILD_DEPENDS example please add it (a TODO comment was added regarding
XXX: that). At least according a quick grep of BUILD_DEPENDS probably most of
XXX: them are actually BUILD_DEPENDS and maybe all real BUILD_DEPENDS are via
XXX: buildlink3.mk inclusion.
Most of the wording was based on the pkglint implementation from before
2015 and was too technical to be useful. Since 2015, bmake doesn't split
the .for arguments on simple whitespace but uses brk_string as well,
therefore that information was outdated.
