all dependencies on packages depending on "png" which contain shared
libraries, all for the (imminent) update to the "png" package.
[List courtesy of John Darrow, courtesy of "bulk-build".]
DEPENDS+= ghostscript-[6-9]*:../../print/ghostscript
and packages needing just any ghostscript binary use
DEPENDS+= ghostscript{,-nox11}-[6-9]*:../../print/ghostscript
denote that the package uses libXaw.
Introduce an XAW_TYPE definition, which is defined in /etc/mk.conf by
the user, to denote the type of libXaw to use. Possible values are:
standard, 3d and xpm.
Define USE_XAW in relevant Makefiles.
Set default XAW_TYPE in Makefiles which previously did a DEPENDS+= Xaw3d...
This means that package builds should not fail because of conflicting
Xaw packages being installed on machines.
build a binary package with this definition would fail as the PLIST is
not correct.
If a package's documentation is overwhelming, it should arguably be handled
in a separate pre-requisite documentation package.
- New, optional Makefile variable HOMEPAGE, specifies a URL for
the home page of the software if it has one.
- The value of HOMEPAGE is used to add a link from the
README.html files.
- pkglint updated to know about it. The "correct" location for
HOMEPAGE in the Makefile is after MAINTAINER, in that same
section.
Implement a new DEPENDS definition, which looks for an installed
package, building it if not present, and use it in preference to
LIB_DEPENDS. This should make the package collection more useful on
NetBSD ELF ports.
ghostscript5 package as (a) we should be encouraging people to use the
packages collection where possible, and (b) it messes up the package
depencies if we don't, to the extent that pkg_delete will have problems.
We need some dependency here, and it's either on ${LOCALBASE}/bin/gs
to pick up the ghostscript 5 package's gs binary, or simply gs, to
pick up any gs binary in the path. The latter was chosen for the
moment.
