From owner-freebsd-ports@FreeBSD.ORG Fri Feb 6 13:52:42 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4156D16A4CE for ; Fri, 6 Feb 2004 13:52:42 -0800 (PST) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAB7B43D1D for ; Fri, 6 Feb 2004 13:52:40 -0800 (PST) (envelope-from parv_fm@mailsent.net) Received: from moo.holy.cow ([69.160.71.102]) by mta10.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040206215240.UCVU14088.mta10.adelphia.net@moo.holy.cow>; Fri, 6 Feb 2004 16:52:40 -0500 Received: by moo.holy.cow (Postfix, from userid 1001) id 379D2B437; Fri, 6 Feb 2004 16:52:44 -0500 (EST) Date: Fri, 6 Feb 2004 16:52:44 -0500 From: parv To: Christopher Nehren Message-ID: <20040206215244.GA1719@moo.holy.cow> Mail-Followup-To: Christopher Nehren , FreeBSD Ports List References: <20040206173646.GA98792@prophecy.dyndns.org> <20040206183841.GB385@moo.holy.cow> <20040206194011.GA1000@prophecy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040206194011.GA1000@prophecy.dyndns.org> cc: FreeBSD Ports List Subject: Re: Suggestion for distinction of XS Perl ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 21:52:42 -0000 in message <20040206194011.GA1000@prophecy.dyndns.org>, wrote Christopher Nehren thusly... > > On Fri, Feb 06, 2004 at 13:38:41 EST, parv scribbled these > curious markings: > > A module is a module is a module. > > > > If we will be having XS modules marked as stated above, i want to > > have module ports marked which are already installed w/ a, 'a' as in > > any, perl version. > > I'm not exactly sure of what you mean by this -- can you elaborate? I did not want to explicitly say that adding 'XS' to a Perl module port's name for the sole reason to make it easy for one person to upgrade was silly. See also... http://groups.google.com/groups?th=69ac9ba85ec82d5a > An alternative method is to have the XS Perl modules depend on > a pseudo-port, and then you can "portupgrade -r perl-xs-package", > and it'd do all of the work for you, like with pkg-config and > GNOME (though that's not a pseudo-port at all, of course). That seems a better/cleaner idea than to put XS in a port's directory name. - Parv --