Hi
I always thought the port: dependency a very nice thing, but I wonder
if it is well suited for libraries. For instance, it would be very
helpful for me to create a glib-devel port. But that would mean
modifying over 60 ports that have a port:glib2 dependency. The same
happened with the gtk28 port and the same is most likely to happen
again.
Any thoughts about this ?
yves
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
