On 28 Jan 2007, at 19:12, Daniel J. Luke wrote:
On Jan 28, 2007, at 6:37 PM, Mark Duling wrote:
Ok, it works. Adding the 'PortGroup perl5 1.0' statement to my port
allowed me to use the variable ${perl5.archlib}, just what I
wanted. The
only remaiing question is when I add the perl portgroup to the
smokeping
port, whether I should move the port to category dports/perl or
leave it
in dports/net with perl as a secondary category.
I don't think it matters if you use the group code in a non perl
category.
Its probably best if you (as the maintainer) decide which
categories the port belongs to.
I personally feel that the language-specific groups (java, perl,
python, etc) only really make sense as the primary group for bindings
or extension to the language. If you have a network application/tool
then I'd put it in the net group.
--
Daniel J. Luke
+========================================================+
| *---------------- [EMAIL PROTECTED] ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
Randall Wood
[EMAIL PROTECTED]
"The rules are simple: The ball is round. The game lasts 90 minutes.
All the
rest is just philosophy."
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
