On May 21, 2009, at 12:29, David Evans wrote:
[email protected] wrote:
--- trunk/dports/gnome/gnome-platform-suite/Portfile 2009-05-09
20:16:23 UTC (rev 50796)
+++ trunk/dports/gnome/gnome-platform-suite/Portfile 2009-05-09
20:40:52 UTC (rev 50797)
@@ -18,6 +18,7 @@
homepage http://www.gnome.org/
master_sites gnome
+depends_build path:bin/pkg-config:pkgconfig
depends_lib port:at-spi \
port:atk \
port:esound \
@@ -39,8 +40,7 @@
port:libxml2 \
port:libxslt \
port:orbit2 \
- port:pango \
- port:pkgconfig \
+ path:lib/pkgconfig/pango.pc:pango \
port:policykit-gnome
distfiles
Ryan --
I agree with your pango change here but with respect to pkgconfig
there was some method to my madness. This is a meta package
that attempts to install a set of ports that the GNOME project
refers to as the GNOME platform modules -- the basic set of packages
needed to develop GNOME applications and they list pkgconfig as one
of these. Thus, it seemed appropriate to me to make it a library
dependency in this case (one that shouldn't be removed after
installation of this port) even though it strictly doesn't provide any
libraries used at run-time and normally would be a build dependency
anywhere else.
Does this make any sense?
Ok, my apologies, feel free to change it back. There was another port
recently where that was given as the reason too.
Also I'm not sure why you made it a path dependency. Should this
be done globally?
I am getting tired of having to monitor ports' dependencies for
things like "port:pango" and "port:cairo" and "port:glib2" and
"port:graphviz" and any other port:-style dependency on something for
which a -devel version exists, and then change it to a path
dependency. :) I'm trying to get in the habit of using a path:-style
dependency always, even if a -devel version does not currently exist,
because maybe tomorrow someone will want to create a -devel version.
We may want to make path:-style dependencies the recommended way to
specify dependencies.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
