Age | Commit message (Collapse) | Author | Files | Lines |
|
a good number of bugs.
|
|
|
|
Use gsort from coreutils instead of /bin/sort if coreutils is installed.
Install coreutils in BULK_PREREQ to get gsort; /bin/sort can't handle the
amazingly long lines produced by the dependency-tree printing script.
|
|
old and buggy, and if a package wants USE_GNU_TOOLS+=awk, pull in lang/gawk
instead for less problems.
|
|
of packages. Several utilities behave differently or even incorrectly if
a locale different than 'C' is set.
One of these is perl, which spits a big warning and then breaks some
packages. An example is irssi, as described in PR pkg/29613 by Hanno
Wagner.
|
|
|
|
before, but after the introduction of alternatives, a regression appeared.
This is useful for packages that install files inside ${PREFIX}/java so
that the directory is automatically removed when empty.
Problem exposed by sablevm-classpath as described in PR pkg/29643 by
Antoine Reilles.
|
|
but can be buggy in some situations (like the bulk build environment).
If pkgsrc gawk happens to be installed, use that; also add lang/gawk to
BULK_PREREQ so it is always used in that case. If lang/gawk is not
installed, ${AWK} will default to /usr/contrib/bin/gawk as it did before.
|
|
possible, just for the sake of doing so, is not a good thing to do:
The platform files define _STRIPFLAG_* to determine whether to strip things.
But since this is included in bsd.prefs.mk, ".if ..." checks cannot take
things set in the Makefile into account. So convert INSTALL_UNSTRIPPED=YES
to a defined/undefined variable check in bsd.pkg.mk, and use the :D:U idiom
in the _STRIPFLAG_* variables.
This should fix PR pkg/28772 and PR pkg/29031.
|
|
|
|
|
|
others as broken
|
|
ultimately selected. PGSQL_TYPE may be used to reference various
BUILDLINK_*.${PGSQL_TYPE} variables.
|
|
|
|
|
|
|
|
package, based on whether /usr/bin/nroff is available).
|
|
but disable this if the package name in the pkg-vulnerabilities file contains
a meta-character. This speeds up the check-vulnerable target from:
[9:28:06] agc@sys3 ...pkgsrc/misc/libutf 11 > time make check-vulnerable
1.821u 1.988s 0:02.57 147.8% 0+0k 0+0io 0pf+0w
[9:28:17] agc@sys3 ...pkgsrc/misc/libutf 12 >
to
[9:28:27] agc@sys3 ...pkgsrc/misc/libutf 13 > time make check-vulnerable
0.273u 0.233s 0:00.33 151.5% 0+0k 0+0io 0pf+0w
[9:28:30] agc@sys3 ...pkgsrc/misc/libutf 14 >
(with caches filled, on a fairly fast machine - P4 2.8 GHz, 2GB RAM).
|
|
available, since the builtin ones aren't so wonderful.
|
|
on some systems, e.g. solaris, will simply drop long lines. These longs
lines are found in the flattened up and down dependency lists in the bulk
cache files. Instead, use sed to deal with this.
Fixes problems noted in Solaris bulk builds. Patch tested on NetBSD-2.0
and Solaris-2.9
|
|
AIX, and AIX ships with perl 5 by default, allow pkgsrc to use it for
building stuff.
|
|
why it must be done this way.
|
|
the file names of libtool archives.
|
|
|
|
Doing so broke any package (such as matlab-mode) where these were not equal,
and in a particularly damaging and non-obvious way.
|
|
PKG_DEBUG_LEVEL > 1.
|
|
not sasl. From Lloyd Parkes in PR 29604.
|
|
It is not defined here though. It is defined in
mk/buildlink3/bsd.buildlink3.mk.
|
|
for a dist file or patch, and let the "checksum" target do the full
digest integrity checks. Should fix a problem reported by John Klos
on tech-pkg, which I was a bit dim in analysing.
|
|
Before this fix it would include
PLIST.common
then _only_ one of the following
PLIST.${OPSYS}
PLIST.${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST.${OPSYS}-${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST
and then PLIST.common_end.
Now, uses all of the following PLIST files, in that order:
PLIST.common
PLIST.${OPSYS}
PLIST.${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST.${OPSYS}-${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST
PLIST.common_end
|
|
|
|
Scheler and Drochner.
Handle missing checksums in distinfo properly.
Tested by myself and tron.
|
|
does. This allows us to use dynamic PLISTs for Perl modules that are
built using Module::Build. Bump the PKGREVISION of p5-Module-Build
to 1.
* Drop the use of PERL5_USES_MODULE_BUILD and introduce a new variable
PERL5_MODULE_TYPE that is either "MakeMaker" or "Module::Build" that
names the framework used to build/install the module.
* Split out the variables set in perl5/buildlink3.mk that are also used
by perl5/module.mk into a new file perl5/vars.mk. Move some PERL5_*
variable definitions from pkgsrc/mk/bsd.pkg.use.mk into perl5/vars.mk.
This just centralizes the common PERL5_* definitions into a single
file location.
* Convert the known packages that use Module::Build to set
PERL5_MODULE_TYPE and PERL5_PACKLIST:
devel/p5-Class-Container
devel/p5-Exception-Class
devel/p5-Log-Dispatch
devel/p5-Array-Compare
textproc/p5-Pod-Coverage
www/p5-Apache-Session-Wrapper
www/p5-MasonX-Request-WithApacheSession
|
|
|
|
|
|
|
|
ensure the integrity of distfiles and dist patches. For now, the
default algorithms are SHA1 and RMD160, set as a whitespace-separated
list in the DIGEST_ALGORITHMS definition. The DIGEST_ALGORITHM
definition is deprecated.
Patchfiles will still use simply SHA1, since we are trying to detect a
binary "has this file changed", rather than proect against tampering.
In short, if someone can modify the patch file, they can modify the
distinfo file holding its digest information. This value is set in the
new PATCH_DIGEST_ALGORITHM definition.
Triggered by the breaking of SHA1, as reported in
http://www.schneier.com/blog/archives/2005/02/sha1_broken.html
|
|
PLIST.common
PLIST.${OPSYS}
PLIST
PLIST.common_end
to
PLIST.common
PLIST.${OPSYS}
PLIST.${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST.${OPSYS}-${MACHINE_ARCH:C/i[3-6]86/i386/g}
PLIST
PLIST.common_end
Which makes it possible to remove duplicated code in some packages.
This doesn't change anything, because all affected packages define PLIST_SRC,
so this code would never be used for them.
And most of them will be fixed with the next commit.
ToDO: ${MACHINE_ARCH:C/i[3-6]86/i386/g} looks wrong and should be changed,
but thats what we allready use for MESSAGE_SRC.
|
|
all grep(1)s support grepping for empty string. `${GREP} .' instead.
|
|
extension when the runtime linker is used. from garbled@.
|
|
are dynamically linking, the -brtl flag must be passed to the linker
so that the runtime linker is used.
tested on AIX 4.3 and 5.1 by garbled@.
|
|
|
|
Mandrake Linux 10.1 as used by A L Meyers has /bin/id.
This should fix his PR #pkg/29430 and #29431.
|
|
current.
|
|
MACHINE_GNU_PLATFORM is set to something sane. tested with AIX 4.3.3
and 5.1.
|
|
|
|
Since the bsd.wrapper.mk framework was introduced, hence the removal
of BUILDLINK_VARS handling from bsd.buildlink3.mk, none of the variables
listed in BUILDLINK_VARS were "cached" in any way.
|
|
|
|
<20050215182853.AC52D3C03B8@berkshire.machshav.com>
The check for a vulnerable package at package fetch time is producing
incorrect results when csh-style alternates are used in the
pkg-vulnerabilities specification of the vulnerable package - disable
the incorrect speed-up that was there previously, at the expense of
some machine cycles at build time.
|
|
statically link the Intel provided libraries.
|