Suggestion for distinction of XS Perl ports

[parv]

in message <20040206173646.GA98792 at 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

--