Suggestion for distinction of XS Perl ports

[Christopher Nehren]

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?

> 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.

I think that something like this[1]:
find ${PORTSDIR} -mindepth 3 -maxdepth 3 -iregex '.*p5.*/pkg-plist' -exec
grep -l '\.so$' {} \;

would work as a good start. Granted, it won't get everything
(razor-agents, for example), but it does get a lot of them --
approximately 240 or so on my machine. 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).

[1]: If desired, I could write a Perl script to recurse through the
ports tree and grep the Makefiles for PERL_CONFIGURE and the pkg-plist
files for '\.so$'. This would probably prove to be a more definitive way
to determine which ports use XS. If anyone knows of a better way to
determine if a port is a Perl XS module, the information would be
appreciated.

-- 
I abhor a system designed for the "user", if that word is a coded
pejorative meaning "stupid and unsophisticated".  -- Ken Thompson
-
Please CC me in all replies, even if I'm on the relevant list(s).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040206/cb60315a/attachment.bin