foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
Speed optimisations:
Reduce number of calls to 'make'
If a package is checked in the '-u' check, skip it in the '-a' check
Features:
Output after the checking phase is now suitable for use as an sh script
Implement '-r' which will recursively delete mismatched packages
Fixes:
Change pkgchk references to pkg_chk
+ Convert a few "grep | awk" pipelines into straight awk.
+ Add in path names per OS.
+ Add a just-in-time su so that pkg_tarup can be run as a normal user, and
the right things will happen.
libraries to ${X11BASE} under ${LOCALBASE}/share/x11-links. It is intended
for use by buildlink code to cleanly separate out the true X11 code files
from any installed X11 package code files. The X11 hierarchies supported
are:
XFree86-3.3.x
XFree86-4.0.x
XFree86-4.1.0
Check during install if packages have already been installed.
Avoids reinstalling a package if it had already been installed as
a depends on a previous package.
installing buildlinkX11.rules as X11.rules via a symlink to ensure that
buildlinkX11.rules gets used in place of X11.rules everywhere. This should
fix pkg/13638 by Martin Husemann <martin@duskware.de>.
- Add Solaris portability fixes supplied by Stoned Elipot in PR pkg/13434.
- Rename binary to "pkg_chk" which matches the naming of our package tools
and avoids confusion with Solaris's "pkgchk" command.
don't use python, set this to NO_PACKAGE to prevent building a binary
package. For now I'll let someone else look at merging this directly
into the python pkg (where it should be).
to install things like "open.3" and "lib.3" which confuse users. Perl
ships with a documentation tool, "perldoc", for this purpose; create a
MESSAGE indicating that it should be used instead. (Perl still installs
command line program manual pages in man1.)
* Integrate bsd.perl.mk into the perl5-base build where it should have been
from the beginning. The separate perl-mk pkg makes binary packages of
perl-mk completely useless[*]. Older perl builders will not break, since
<bsd.pkg.mk> contains fallback definitions that are evaluated at pkg
build time.
=====
[*] bsd.perl.mk is tightly bound to the version of perl that is installed.
The version name "perl-mk-1.1" is completely useless as a binary pkg,
since keeping multiple binary versions of perl on a FTP server means
that one of the perl-mk's will get clobbered.
However, putting the current pkgsrc PERL5_DIST_VERS in the perl-mk pkg
is also a problem, because that doesn't necessarily reflect the
installed version of perl. Snarfing the installed version at perl-mk
build time would be even uglier, since you could not then walk the tree
without perl being installed.
The cleanest solution is to integrate bsd.perl.mk into the perl5-base
pkg, and let those who have not upgraded perl yet use the runtime
definitions in <bsd.pkg.mk>.
