From owner-freebsd-ports@FreeBSD.ORG Tue Jul 24 17:32:56 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6C6416A417 for ; Tue, 24 Jul 2007 17:32:56 +0000 (UTC) (envelope-from tobez@tobez.org) Received: from heechee.tobez.org (heechee.tobez.org [194.255.56.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6BB3B13C45B for ; Tue, 24 Jul 2007 17:32:56 +0000 (UTC) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id 69C7F125420; Tue, 24 Jul 2007 19:32:55 +0200 (CEST) Date: Tue, 24 Jul 2007 19:32:55 +0200 From: Anton Berezin To: Paul Schmehl Message-ID: <20070724173255.GB42493@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Paul Schmehl , FreeBSD Ports References: <20070724095718.GB68140@heechee.tobez.org> <1B50EA71ECD75693D12CE9D3@utd59514.utdallas.edu> <20070724142514.GA4315@heechee.tobez.org> <69DD0E3AC68E2AEC7C876B4C@utd59514.utdallas.edu> <20070724161616.GA42493@heechee.tobez.org> <94D0B4C06F1B6E62AF90AEED@utd59514.utdallas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94D0B4C06F1B6E62AF90AEED@utd59514.utdallas.edu> User-Agent: Mutt/1.4.2.3i X-Powered-By: FreeBSD http://www.freebsd.org/ Cc: FreeBSD Ports Subject: Re: How to include new dirs in @INC X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2007 17:32:56 -0000 On Tue, Jul 24, 2007 at 12:03:48PM -0500, Paul Schmehl wrote: > --On Tuesday, July 24, 2007 18:16:16 +0200 Anton Berezin > wrote: > >Right. I assume that the port you are creating uses "normal" Makefile.PL > >for a part of the configuration process, while not being the main > >configuration mechanism (that is, the port does not define PERL_CONFIGURE > >in its skeleton). > Yes, but it also uses GNU_CONFIGURE for the main parts of the port. > Is it possible to use both GNU_CONFIGURE *and* PERL_CONFIGURE? Nope, not to my knowledge. > I'll poke around. > Maybe I could pre-build the perl parts? This is a very complex port. Well, it certainly sounds like it is. There are other ports that do something similar, however, for example net/spread. In fact, what it does looks almost exactly like what you need. \Anton. -- We're going for 'working' here. 'clean' is for people with skills... -- Flemming Jacobsen