perl or net category? - was variables and external cmds / ${perl5.lib}

[Daniel J. Luke]

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.

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20070128/e94876ab/PGP.bin