[50797] trunk/dports/gnome/gnome-platform-suite/Portfile
David Evans
devans at macports.org
Thu May 21 10:29:19 PDT 2009
ryandesign at macports.org wrote:
>
> Revision
> 50797 <http://trac.macports.org/changeset/50797>
> Author
> ryandesign at macports.org
> Date
> 2009-05-09 13:40:52 -0700 (Sat, 09 May 2009)
>
>
> Log Message
>
> gnome-platform-suite:
>
> * allow pango-devel to satisfy pango dependency
> * pkgconfig is a build dependency, not a library dependency
>
>
> Modified Paths
>
> * trunk/dports/gnome/gnome-platform-suite/Portfile
> <#trunkdportsgnomegnomeplatformsuitePortfile>
>
>
> Diff
>
>
> Modified: trunk/dports/gnome/gnome-platform-suite/Portfile
> (50796 => 50797)
>
>
> --- 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? Also I'm not sure why you made it a path
dependency. Should this be done globally?
Dave
More information about the macports-dev
mailing list