| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
instead on perl>=5.8.0. Bump the PKGREVISIONs of the following packages
due to the possible perl dependency changes after the removal of
libperl:
audio/ices-mp3
databases/postgresql73-plperl
databases/postgresql74-plperl
textproc/eperl
www/ap-perl
|
|
|
|
Plan:
(1) Change USE_PERL5=build into USE_TOOLS+=perl.
(2) Change all other USE_PERL5 into including perl5/buildlink3.mk.
Possibly, for packages that don't actually build anything with perl,
but merely require it for the perl interpreter, we can instead do:
USE_TOOLS+= perl
TOOLS_DEPMETHOD.perl= DEPENDS
but this is more verbose than simply including the perl5/buildlink3.mk
file.
Move the PERL5_REQD computation into a lang/perl5/version.mk file,
and only do the USE_PERL5 logic in bsd.pkg.use.mk if we're not using
the new tools framework. This consolidates all of the perl-handling
into two places -- lang/perl5 and mk/tools/perl.mk.
|
|
|
|
|
|
building libperl.
|
|
for this package.
|
|
|
|
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
|
|
|
|
|
|
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example
buildlink[23].mk files in bsd.buildlink[23].mk.
|
|
available.
|
|
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
to choose the correct Perl dependency.
|
|
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
|
|
|
|
recommended by seb :)
|
|
|
|
buildlink3 framework.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DynaLoader.a is now an archive of PIC objects.
|
|
from the distfile version number. G/C the version number stuff from
perl5/Makefile.common, preserving only PERL5_DIST_VERS as it's still used
by libperl.
|
|
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
|
|
|
|
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
|
|
|
|
the plugging of several memory leaks, fixes to the regular expression
engine, the addition of a Unicode character classes, better support for
64-bit platorms, and updates of many modules in the base Perl Library.
See perldelta.pod for more details.
Also update p5-Data-Dumper, p5-Devel-DProf, and p5-Devel-Peek to the
latest versions distributed with the perl-5.6.1 sources, and libperl to
5.6.1 to match the perl package.
|
|
|
|
|
|
5.6.0nb1 as this package no longer builds and installs libperl.so as a
shared library. Instead, libperl.so is built and installed by the perl
(as of 5.6.0nb6) if the platform supports shared libraries (or if
MKPIC=yes). The libperl package again only installs DynaLoader.o as a
relocatable shared object.
|
|
|
|
|
|
back a dynamic libperl.so to the installation, needed as a result of a
change made on 2000-11-08 to the perl5-base package to not build against a
dynamic libperl.so.
|
|
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
package Makefile.
|
|
|
|
${PERL5_ARCHLIB}/DynaLoader_pic.o, which contains the dynamic loader in
dynamically loadable form. This is needed by ap-perl.
|
|
|
|
|
|
distribution in pkgsrc.
|
|
appropriate.
|
|
|
