Re: gtk-engines photographed eating children
- From: Andrew Johnson <ajgenius ajgenius us>
- To: GNOME Desktop Hackers <desktop-devel-list gnome org>
- Cc: Jeff Waugh <jdub perkypants org>
- Subject: Re: gtk-engines photographed eating children
- Date: Tue, 25 Jan 2005 01:16:11 -0500
Actually gtk-engines has had a pkgconfig file for a long time, at least
since 2.2, this is nothing new and certainly nothing we messed with, and
gnome-themes has had this dependency since before 2.6 as well, so again
nothing new - we didn't add it.
The only difference is the gtk-engines version dependency has been
upped. I guess its sort of because otherwise gnome-themes could be built
with gtk-engines 2.2 installed which would result in half the themes not
working due to missing/too old engines. Realistically though it makes no
difference whatsoever for binary packages, and is only there too serve
as an annoying warning/error for those building from source. It probably
could be abolished.. I have never fully seen the need for a gtk-engines
module to have a .pc file.
Andrew
On Tue, 2005-01-25 at 17:02 +1100, Jeff Waugh wrote:
> <quote who="Jeff Waugh">
>
> > I still don't understand why we're stuck with two modules here...
>
> One of the other entertaining aspects of these two modules: gtk-engines now
> has a pkgconfig file for seemingly no other reason than letting gnome-themes
> break its build if it can't find it. It doesn't even require any info from
> the pkgconfig file...
>
> ubuntu: ~/src/gnome-themes-2.9.90
> $ grep -rl gtk-engines-2 *
> configure
> configure.in
>
> - Jeff
>
--
Andrew Johnson <ajgenius ajgenius us>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]