From owner-freebsd-ports  Tue Mar 25 05:48:51 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA12735
          for ports-outgoing; Tue, 25 Mar 1997 05:48:51 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (ala-ca8-54.ix.netcom.com [207.93.141.182])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12730
          for <ports@FreeBSD.ORG>; Tue, 25 Mar 1997 05:48:49 -0800 (PST)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id FAA00913; Tue, 25 Mar 1997 05:48:36 -0800 (PST)
Date: Tue, 25 Mar 1997 05:48:36 -0800 (PST)
Message-Id: <199703251348.FAA00913@silvia.HIP.Berkeley.EDU>
To: imp@village.org
CC: ports@FreeBSD.ORG
In-reply-to: <E0w9BUF-00056x-00@rover.village.org> (message from Warner Losh on Mon, 24 Mar 1997 08:16:38 -0700)
Subject: Re: Perl
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * :  * do-configure:
 * :  * 		@ cd ${WRKSRC}; ${SETENV} ${MAKE_ENV} ${PREFIX}/bin/perl Makefile.PL
 * : 
 * : I don't understand what HAS_PERL_CONFIG is supposed to do.  Do some
 * : perl packages come with this Makefile.PL file that is actually not a
 * : Makefile but is a configure script?
 * 
 * Almost none of them come with Makefile.PL that isn't a config script.

Ok...but is it necessary to run it?  (The current perl ports don't run 
it, right?)

Also, is it possible to just use the existing framework (CONFIGURE_*)
to do it?  (Taking a quick look at bsd.port.mk, I see a "./" in front
of ${CONFIGURE_SCRIPT}, that much at least has to be changed though.)

 * It doesn't detect perl5 existing all of the time.  At least that's my
 * experience.  

Then I'm afraid there is something wrong with your system.  It's just
a simple "which" test so it should always be found or never found (if
you don't have /usr/local/bin in your path).

 * 		And *_DEPENDS make the whole build fail, rather than just
 * this port, at least that's how it appeared to be acting when I've been
 * building under OpenBSD.

There is nothing wrong with this.  If you do a top-down build without
"-k", and one of the ports fail to build, make is supposed to stop.

 * If I want to build the ports tree, but I don't care about any of the
 * P5-* ports for whatever reason, I'd like to be able to disable them
 * easily.

If you are going to build the whole ports tree, there are many ports
that (by itself) install much more junk than all the p5-* ports
combined. :)

Satoshi