Age | Commit message (Collapse) | Author | Files | Lines |
|
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
|
|
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
|
|
python3, since the default changed from python33 to python34.
I probably bumped too many. I hope I got them all.
|
|
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
|
|
This broke packages that needed a target Python at build-time.
Instead, change it from defined/undefined to yes/no/tool. Most cases
of defined used `yes' anyway; fix the few stragglers do that instead.
New case `tool' is for TOOL_DEPENDS rather than buildlink3.
|
|
Change "-W," to "-Wl," in configure script.
GCC 4.7.2 doesn't let the typo pass like order GCCs do.
|
|
are called p5-*.
I hope that's all of them.
|
|
|
|
Bump package revision.
|
|
installs, among its documentation, an extra empty file called
pfe-manual.proc.
It's been failing in ~every bulk build, so I'm just going to add the
thing to the PLIST unconditionally. And because of the total
unimportance of the extra file, I'm not going to bump the package
revision.
|
|
Bump PKGREVISION
|
|
worse, a csh, to run libtool and maybe other things.
|
|
|
|
The Portable Forth Environment (PFE) is portable, modular, and
extensible in run time Forth programming environment, based on
the ANSI Standard for Forth.
|