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.
- Document the `current', `stable' and `pkgsrc-20xxQy' more extensively,
from J. Lewis Muir via PR pkg/54019. Thanks!
- Refers to `pkgsrc.tar.{bz,gz,xz}' instead of just `pkgsrc.tar.gz' to
cover all compressed formats.
- Document `pkgsrc-readmes.tar.{bz,gz,xz}'
Despite most CONFLICTS are automatically detected at package
installation time it is still a good idea to manually mark CONFLICTS
in order to fail as early as possible instead e.g. of failing at
package installation time after possibly installing several (maybe
not needed) dependencies.
Pointed out by discussion on pkgsrc-changes@ by <jperkin>:
<https://mail-index.NetBSD.org/pkgsrc-changes/2018/09/09/msg180626.html>
Last two paragraphs from <jperkin>, thanks!
Also discussed with <wiz>, thanks!
Since the latest pkgsrc stable releases htdocs/share/xml/misc.ent had several
XML pkgsrc related entities added and picked up via htdocs-share-*.tar.gz
distfile.
Use them instead of hardcoding a particular stable branch/release (e.g. 2009Q1
or 2016Q4) or using `pkgsrc-20xxQy' (Yay! Now `The pkgsrc guide' should be ready
for the next century!).