installed version and binary packages. The size can be queried then
via pkg_info:
xfeyrer @ noon% pkg_info -s xv
Information for xv-3.10apl1:
Size of this package in bytes: 4670692
xfeyrer @ noon% pkg_info -S xv
Information for xv-3.10apl1:
Size in bytes including required pkgs: 14610165
While doing work on the size code, support for the @src directive was
removed (formerly enabled with the pkg_create -s switch, but unused in
our pkg system). The new pkg_info -s and -S switches were tested on
installed, local (file) and remote (ftp) packages.
In bsd.pkg.mk, take special care for pkg_* versions that do not have
the pkg_create -s and -S switches and do not record size information
there.
USE_FORTRAN should be set in the package Makefile. The logic added by this
commit will choose a fortran compiler to use and set the correct dependency
rather than having this selection scattered across each package which needs
a fortran compiler.
- Add PKG_FC variable. By setting PKG_FC in /etc/mk.conf, users can force the
selection of which fortran compiler gets used by the package system. If not
specified, PKG_FC defaults to f2c-f77 on pre-1.4 systems that did not include
/usr/bin/f77. In addition PKG_FC defaults to f2c-f77 on newer systems since
f77 is still somewhat buggy. When /usr/bin/f77 becomes more stable, the
default should be changed from f2c-f77 to f77.
MASTER_SITE_BACKUP doesn't end in //.
For this, any setting of MASTER_SITE_LOCAL in /etc/mk.conf must no longer
include ${DIST_SUBDIR} - this will be added automatically, if needed.
if patch(1) is smart enough (i.e. not Solaris by default). Also
introduce a second patch stage (in the package patch phase, not the
distribution patches), whereby a misapplied patch with
${PATCH_FUZZ_FACTOR} will be tried again without a fuzz factor. This
will fail on package patches which patch many files, but these should
be fixed anyway.
PLIST, as shared objects. Tested with both GNU egrep and Solaris XPG4
egrep. Not the most compact of regular expressions, due to
non-portability of {n,m} repetition atoms between different versions
of egrep.
Here is a summary of the changed behaviour:
* A "make update" will no longer clean the subtree before running.
* If called a second time, it will resume package installation, in
case a previous "make update" was interrupted for some reason.
(just make sure you don't call "make clean" in between ;-)
* Unless "NOCLEAN" is set, "make update" will clean up the subtree
after successfully updating _all_ packages (to avoid a dirty directory
structure for future makes).
* A "clean-update" target has been introduced to clean up the subtree
that gets updated. This should be used prior to an initial "make
update" if you suspect that one of the packages that get updated may
be dirty.
XXX: this still does not automatically check for or update any obsolete
´upstream' packages (e.g., if gtk depends on glib, a "make update"
in the gtk directory won't automatically update glib, you have to
do it the other way round).
- substitute leading tabs with spaces in IRRD_USE_PGP comment
- use ``YES'' instead of ``yes'' for appropriate variables
- move GLX_CHIPSET, INN_DATA_DIR and KNEWS_* so that the variables are sorted
alphabetically
- add description of possible values for USE_GIF
- comment out NMH_MTA (nmh Makefiles DTRT)
- append = to variables as appropriate so that make(1) will parse them
correctly if they are uncommented
Other minor cleanups:
- s/set, not set/defined, not defined/ in comments
- use empty value consistently for variables whose only purpose is to
be either defined or undefined (previously, either ``yes'', ``1'' or
empty value was used)
- mark variable UVM as obsolete (XXX it should be g/c'ed probably)
show-downlevel target) is a shell glob pattern, not a regular expression,
so wildcards are '*', not '.*'. Due to the format of package names, the
regular expression will match in most cases (a single digit major version
number), but that's no excuse.
the fix from The Wiz in pkg PR 8597. This will still produce erroneous
results for the foo-current vs. foo package discrepancy, but that's left
as an exercise for a later day.
if and only if there are no patches and patch-sum already exists.
This is necessary to meet the original purpose of that target, which
is to "catch" users who happen to have old patches lying around,
for whatever reason. Also, don't update patch-sum if it wouldn't change.
