Suggestion for distinction of XS Perl ports

parv parv at pair.com
Fri Feb 6 13:52:42 PST 2004


in message <20040206194011.GA1000 at 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

-- 



More information about the freebsd-ports mailing list