I now remember why I felt there was something wrong with the fix in PR
11433: it calls some target with PACKAGE_DEPENDS_WITH_PATTERNS=false, and
this will cause problems when someone has a different version installed
than what's currently in pkgsrc.
This was also what the XXX was for that I couldn't remember - all
dependencies were found installed at the time that the
print-pkg-size-depends target gets called, and as such we can call
run-depends list with the PACKAGE_DEPENDS_QUICK switch (to first print our
direct dependencies, and then look at their @pkgdep lines to get all their
depends - no need for recursion, as well store all a pkg's depends in it's
@pkgdep lines!). Using that, we can call "pkg_info -e" on all the patterns
to expand them to match what's really installed on the system, then make
that list unique (so that e.g. foo-1.0 and foo-* gets to the same pkg
twice, and then sorted out). After that we can calculate it's size as
before using "pkg-info -s".
Using this method is also a whole lot faster (due to no recursion).
instead; install more documentation.
Lame isn't any longer a patch against the ISO source, but stand-alone.
Other changes:
MP3 decoding support, ID3V2 support, vorbis support (not compiled in
right now), MPEG2.5 support; lots of bugfixes and speedups (for
details, see installed history.html).
via a tmp file. Also, there's no need to excape any possible HTML chars
(there won't be any in a PKGNAME).
Noted in PR 11462 by Jeremy C. Reed <reed@reedmedia.net>
the new version of xpkgwedge. Changes from xpkgwedge 0.4:
* Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to
pick up X11 config files in $(PREFIX)/lib/X11/config before the
ones in the standard X11 tree.
* Install a program called "pkgxmkmf" that's actually xmkmf, but
checks in $(PREFIX)/lib/X11/config before the standard X11 config
directory.
* Create the host.def file in $(PREFIX)/lib/X11/config instead of
always in ${X11BASE}/lib/X11/config.
The benefits of this are:
1) xpkgwedge can now install into $(PREFIX) instead of always into
$(X11BASE).
2) Keeps the X11 tree "pure", and doesn't affect people who want
to run xmkmf and not include all the xpkgwedge stuff, even if
it's installed.
3) Packages that install config files (lesstif, xview-config) can
now do so in $(PREFIX).
4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and
(hopefully) no other changes, if they want to use the config
files in xpkgwedge'd packages.
jdk 1.1.8 and the blackdown-jre 1.2 will work (and make the version just *,
not 1.1.*). This is a precursor to native JDK 1.2 support. Leave the
preference of the dependency to use the native jdk 1.1.
XXX: There should be a standard location not specific to PKG_JAVA for Java
packages, and there is no particular need for a DEPENDS on the JVM for
most packages (even an external-to-tree JVM is typically happy with the code).
This per-VM PREFIX, and particularly configurable JAVA_HOME, is not clean.
from the middle of root-install until the end of fake-pkg target. At
the end of the fake-pkg target, the package has been registered using
pkg_create(1), and so it's possible to use relational comparisons of
the version numbers, thereby making it possible to use the information
from the standard vulnerabilities file.
This addresses PR 11077.
can either be defined or not. This governs the installation of the
floppyd binary in the mtools package. The floppyd program needs
the SM and ICE libs from the X11 distribution to link (floppyd's
authorisation model to enable remote access to floppy drives closely
resembles that of X11's xauth model). Modify the mtools Makefile
accordingly.
* Prefix every line of the build's output with the architecture, so it's
easy to see at a glance which architecture you have scrolling by in
front of you
It use the wrong ls when you have /usr/ucb before /usr/bin in your PATH.
The usb-ls doesn't print the group field, so the size is the 4th field and
not the 5th one.
Fixed by using the /usr/bin one.
Added and use: ${LS} which points to the correct ls.
Also add a space after the 0 in the AWK part of this target and one after
the '+'. Noticed by Klaus Klein.
Changes reviewed by Hubert Feyrer.
sun-jsdk20-license and sun-swing-license), and what licenses they correspond
to.
It is especially important that people do not blindly add these values to
ACCEPTABLE_LICENSES, as these values indicate that the user has read and
accepted specific license agreements, not general terms of redistribution
as with the `generic' LICENSE values.
on tech-pkg. Setting either USE_SSL or CRYPTO in the package's
Makefile will permit the package to build or not, depending on the
setting of MKCRYPTO (set to yes by default).
we actually check for "X", and not just Motif. Also, clean up word
wrap, and rearrange the sections to be in the same order as the checks
they refer to.
sets MKCRYPTO=no, packages in this category won't be fetched, installed,
built, or packaged. Also, binary package users forbidden, by law, from
using strong cryptography would presumably find the list on the category's
automatically generated web page useful for ensuring compliance.
On 'make reinstall', the DEPENDS_TARGET is also set to reinstall, and for
pkgs with dependencies this results in all dependencies being removed and
reinstalled.
to precent check-shlibs from discovering that ldd(8) can't deal with
e.g. Linux binaries
* On "make reinstall", make sure the package gets deinstalled first.
No more 'make deinstall ; make reinstall'.
type of the file and additional information in successive fields of the
packlist. Note that this will break if the installed filenames have spaces
in them, which I don't think happens, yet.
* Add a PERL5 variable that is always defined, set to the path of a
pkgsrc-installed perl5 binary (${LOCALBASE}/bin/perl).
* Define three new variables PERL5_SITELIB, PERL5_SITEARCH, and
PERL5_ARCHLIB that define special locations used by perl. In
particular, it seems packlists are always found under PERL5_SITEARCH.
* Substitute the above three variables when generating PLISTs, but
stripping away the initial ${LOCALBASE}/ part. This is for perl
packages which don't generate packlists because they don't use the
perl Makefile generator during the build process.
* Append to the PLIST any files listed in the packlists named by
PERL5_PACKLIST. Also append statements to try removing the
directories installed into by the packlist-ed files.
- quote arguments to pkg_admin so the shell doesn't try to expand any *'s.
- be sure that all required binary packages exist. The previous version
made sure the required packages were not newer, but missed catching missing
required packages.
Still todo:
When examining required binary packages to see if they have changed, the test
only looks at the modification time of the binary package. It does not verify
that the required binary package is also up to date with respect to its
pkgsrc files.
whether the proper shared libs are available. Packages which use the
emulation system should set LDD to the path of a the emulated ldd, or
simply set it to true, e.g.:
LDD?= /emul/linux/usr/bin/ldd
LDD?= ${TRUE}
Fixes PR#10853.
from producing errors
* Rework IGNORE handling:
- IGNORE messages must now include the pkg's name
- if multiple reasons exist for a pkg to be ignored, they are now
all printed
- IGNORECMD is gone
* Make 'mirror-distfiles' not print a warning if NO_SRC_ON_FTP is
set (I really don't want to see that list every day!)
* Catch one leftover 'depends' -> 'install-depends'
* Replace NO_CDROM with NO_SRC_ON_CDROM and NO_BIN_ON_CDROM
* Add NO_{SRC,BIN}_ON_{FTP,CDROM} to BUILD_DEFS (in case someone
wants to re-distribute a binary pkg, so he has a chance to know
about resitrictions)
* Adjust 'mirror-distfiles' target for NO_SRC_ON_FTP
