PERL_LEVEL conditional dependencies
Ade Lovett
ade at FreeBSD.org
Wed Aug 11 13:02:58 PDT 2004
On Aug 11, 2004, at 10:29, Sergey Skvortsov wrote:
> I think your patch for p5-File-Temp:
>
> .if ${PERL_LEVEL} > 500800
> IGNORE= "This module is already included in perl 5.8.x and later."
> .endif
>
> is senseless and detrimental.
Ok, let's slow down a bit here. This is obviously an issue that is
likely to cause much consternation (I'm specifically avoiding use of
the "b-word" here :)
> All p5-ports with IGNORE like "This module is already included in perl
> X.Y.Z" should be cleaned up.
Well, the standard answer to that would be "patches welcome", but is
not particularly useful at this point.
Going forward, I would *strongly* recommend that all the perl hooks
etc. be pulled out into a Mk/bsd.perl.mk -- this is an absolute
requirement if further work is to be done on the ports infrastructure
as it relates to perl, since we don't want to be tied into the primary
bsd.port.mk.
Once the first "null-commit" has happened (bsd.port.mk ->
bsd.port.mk/bsd.perl.mk) then, and only then, will it make sense to
start working on a (new/improved/better/whatever) perl port
infrastructure. Initial testing can be thrown around by adding to
bsd.perl.mk in the presence of a specific all-encompassing-variable
(eg: USE_PERL_NEW_WORLD_ORDER=YES :) so that regular end-user
consumers of the perl ports won't see *any* changes until the switch is
flipped.
Then, and only then, will it be possible to sit down, write up what
works, and what doesn't, with the current system, create a wishlist,
and then get down to the coding work, handing out a few more PhD's in
make(1) operation :)
Having recently done the work to extract GNU autotools from bsd.port.mk
into its own standalone file, and being a big consumer of perl ports
myself, I'm certainly willing to offer my services in getting a
bsd.perl.mk set up.
-aDe
More information about the freebsd-perl
mailing list