From owner-freebsd-ports@FreeBSD.ORG Fri Feb 6 10:38:48 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 337A516A4CE for ; Fri, 6 Feb 2004 10:38:48 -0800 (PST) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1992A43D58 for ; Fri, 6 Feb 2004 10:38:43 -0800 (PST) (envelope-from parv_fm@mailsent.net) Received: from moo.holy.cow ([69.160.71.102]) by mta11.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040206183842.OWHI7858.mta11.adelphia.net@moo.holy.cow>; Fri, 6 Feb 2004 13:38:42 -0500 Received: by moo.holy.cow (Postfix, from userid 1001) id 83650B437; Fri, 6 Feb 2004 13:38:41 -0500 (EST) Date: Fri, 6 Feb 2004 13:38:41 -0500 From: parv To: Christopher Nehren Message-ID: <20040206183841.GB385@moo.holy.cow> Mail-Followup-To: Christopher Nehren , FreeBSD Ports List References: <20040206173646.GA98792@prophecy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040206173646.GA98792@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 18:38:48 -0000 in message <20040206173646.GA98792@prophecy.dyndns.org>, wrote Christopher Nehren thusly... > > > While trying out a threaded Apache (and thus a threaded Perl), > I read that I had to reinstall all of my XS modules. So, off to > "portupgrade -f 'p5-*'" [...] But that's hitting a lot of modules > that don't use XS. Would it be unfeasible to demarcate XS modules > by package name, like p5-DBI-XS? 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. > Then I can do "portupgrade -f 'p5-*XS*'" and just get the XS > modules. I'm not fully knowledgeable about how the ports tree > works with something like this A port's files must have something that can identify it is a XS port; something in pkg-descr, reference to compiler in Makefile, pod, etc. - Parv --