RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
It is more consistent with the tex.buildlink3.mk name. Also, if a package
really needs latex, it just has to set TEX_ACCEPTED to latex distributions
altough today, all TEX_ACCEPTED possibilities are latex distributions
Fixed
- src/kernel/sparcv8/MakeVar.SH missing from MANIFEST (hence from tarball)
- stack corruption in matsnf() [ when GC occurs ]
- incorrect result in gaffsg(s < 0, t_PADIC)
- [hi-res plot: X-Windows] rescaling bug
- [ix86 + gcc]: fix "invalid preprocessing token" Warning
- removed hack in buchall() [ function called through unappropriate
type (in init mode) to avoid inserting irrelevant arguments ]. Caused
some compiler to produce incorrect code (SEGV).
- typo in isabsolutepol(): SEGV in factorff for some t_POLs
defined over the prime field
- inconsistent error message when starting 'gp -p 436273000'
- Configure support for GNU/Hurd
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.
Remove `-p' from mkdir arguments, it is already part of ${MKDIR}.
While here substitute a couple of ${PREFIX} by `%D' in
`@exec ${MKDIR} ...' lines and add a couple of missing `%D' in such lines too!
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".]
Fixed
1- return() could forget objects on heap [F2]
2- polhensellift(x^3+x^2+2,[x^2,x+1],2) --> pols not coprime [F3]
3- Configure missed some shared libraries [e.g RedHat 7.0] [F4]
4- requests for precision of bnfinit(x) [ = Q ] could yield SEGV [F6]
5- compatible = 3 not taken into account when reading a file [F7]
6- lines > 0: output driver didn't reset properly after user output [F9]
7- nfdisc(x^5+2*x^4+3*x^3-3*x^2+122*x-1) --> impossible inverse [F10]
8- bug in gcc-2.95: SEGV on Linux (quicksqri) [F11]
9- addrfrac: could return a t_RFRAC whose denominator wasn't a t_POL[F12]
10- bnfcertify (zimmertbound): off by two error when reading bound [F13]
BA 11- pbs in Fp_factor_irred (factoring over Fq a pol. defined over Fp)[F25]
12- typo in quadhilbertimag (SEGV for very large discriminants) [F28]
BA 13- isprime(n < 2, 2 or 3) gave wrong result [F31]
BA 14- nfgaloisconj(polcyclo(11)+1)--> oo loop [F35]
nfgaloisconj(polcyclo(40))-->incorrect result
IS 15- typo in squfof tuning on 64bit machines [F36]
16- van Hoeij's algorithm (factor(Z[X])): wrong bound in LLL_cmbf [F41]
17- rare SEGV in nfdisc [F44]
18- rare problem in isprincipal (large non Galois base field) [F56]
--> wrong result (generators not required) or infinite loop.
19- build failed with readline-4.2 [F57]
Changed
1- DOS distribution archives (GPM removed) [C1]
XR 2- try more prime ideals in nfsqff [nffactor, modular part] [C4]
3- renamed library function gsize() to sizedigit() [pb with gtk] [C10]
IK 4- let lisGEN() return NULL when EOF is met (was oo loop) [C12]
5- install the whole distribution (see ?12) + improved Configure [C17]
Added
1- README.WIN, config/[arch-osname|locatesymbol], doc/tex2mail.1 [A1]
* Install library as libpari.a. (Previously the package installed
libpari.a.2.1 and created a symbolic link libpari.a).
* Fix warning about O_RDONLY being redefined.
first component is now a package name+version/pattern, no more
executable/patchname/whatnot.
While there, introduce BUILD_USES_MSGFMT as shorthand to pull in
devel/gettext unless /usr/bin/msgfmt exists (i.e. on post-1.5 -current).
Patch by Alistair Crooks <agc@netbsd.org>
PARI-GP is a package which is aimed at efficient computations in
number theory, but also contains a large number of other useful
functions. It is somewhat related to a Computer Algebra System, but
is not really one since it treats symbolic expressions as mathematical
entities such as matrices, polynomials, series, etc..., and not as
expressions per se. However it is often much faster than other CAS,
and contains a large number of specific functions not found elsewhere,
essentially for use in number theory.
This package can be used in an interactive shell (GP) or as a C/C++
library (PARI). It is free software, in the sense of freedom AND 'free
of charge'.
