From owner-freebsd-ports@FreeBSD.ORG Tue Feb 26 12:42:09 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05F11106567D; Tue, 26 Feb 2008 12:42:09 +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 D040A13C4E1; Tue, 26 Feb 2008 12:42:08 +0000 (UTC) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id A6B206D402; Tue, 26 Feb 2008 13:25:12 +0100 (CET) Date: Tue, 26 Feb 2008 13:25:12 +0100 From: Anton Berezin To: Yen-Ming Lee Message-ID: <20080226122512.GA30778@heechee.tobez.org> Mail-Followup-To: Anton Berezin , Yen-Ming Lee , Dag-Erling Smorgrav , ports@freebsd.org, perl@freebsd.org References: <86zltpzrxt.fsf@ds4.des.no> <759236930802242324o614598d1i1a8ca3cc8c12478c@mail.gmail.com> <86prulibf4.fsf@ds4.des.no> <759236930802250245j646f5be5k8382bedbfb2a7c1e@mail.gmail.com> <868x19i6ky.fsf@ds4.des.no> <759236930802251702h694c4f5bn2c7c87c7c47c7cc@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <759236930802251702h694c4f5bn2c7c87c7c47c7cc@mail.gmail.com> X-Powered-By: FreeBSD http://www.freebsd.org/ User-Agent: Mutt/1.5.17 (2007-11-01) Cc: ports@freebsd.org, Dag-Erling Smorgrav , perl@freebsd.org Subject: Re: Port dependencies on p5-Test-* 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, 26 Feb 2008 12:42:09 -0000 On Mon, Feb 25, 2008 at 05:02:59PM -0800, Yen-Ming Lee wrote: > So, there are two problems in the current perl ports, and either one > of them will generate the overkill dependencies: > 1. depends on the modules which are in perl core list already A side-line comment here. One has to remember that modules which are in perl core consitute moving targets: 1. Such a module (not only Test::More) might be in the core 5.8 but not 5.6 (or, in the near future, in core 5.10, but not in 5.8 and 5.6). 2. It might be more recent as a stand-alone module than in at least one of the supported cores, and 2a. The module which depends on such *needs* the more recent version. 2b. The module which depends on such can do perfectly well with an older version. As time goes on, these situations will inevitably transmogrify into one another. This means that a scripted solution for such cases will be very prone to errors, and a manually chosen approach will have to be re-examined every time the target port is updated (and possibly every time one of the cores gets updated). I almost wish to rip off dual-life modules from our cores to simplify situation. \Anton. -- We're going for 'working' here. 'clean' is for people with skills... -- Flemming Jacobsen