Date: Fri, 6 Feb 2004 13:38:41 -0500 From: parv <parv@pair.com> To: Christopher Nehren <apeiron@comcast.net> Cc: FreeBSD Ports List <ports@freebsd.org> Subject: Re: Suggestion for distinction of XS Perl ports Message-ID: <20040206183841.GB385@moo.holy.cow> In-Reply-To: <20040206173646.GA98792@prophecy.dyndns.org> References: <20040206173646.GA98792@prophecy.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040206183841.GB385>