use_gnomeng

Doug Barton DougB at FreeBSD.org
Sun Apr 20 15:19:28 PDT 2003


On Sun, 20 Apr 2003, Joe Marcus Clarke wrote:

> On Sun, 2003-04-20 at 17:20, Adam Weinberger wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > >> (04.20.2003 @ 1406 PST): Doug Barton said, in 0.6K: <<
> > > On Sat, 19 Apr 2003, Joe Marcus Clarke wrote:
> > >
> > > > >   How about a port that just uses gtk12?
> > > >
> > > > USE_GNOME=	gtk12
> > >
> > > I'm going to keep bringing this up, since it keeps not getting addressed.
> > > Ports that ONLY want gtk should not need USE_GNOME. The USE_GTK knob
> > > should be preserved ad infinitum.
> > >> end of "Re: use_gnomeng" from Doug Barton <<
> >
> > Doug -
> >
> > USE_{GTK,ESOUND,IMLIB} are still defined in bsd.gnome.mk.
>
> Still defined now for backwards compatibility.  However, this won't
> always be the case.

That's your plan anyway, however it's the plan that is currently under
discussion.

> > However, Doug, if somebody uses USE_GTK instead of USE_GNOME=gtk12, they
> > are also then unable to use other useful gnome macros such as
> > gnomeprefix and gnomehack.

I'm talking about apps which use gtk that don't use any part of gnome.
There seems to be a common misconception that gtk is part of gnome. It
isn't. Ports that ONLY need gtk should not be dragging a bunch of gnome
stuff in with it.

> > That being said, I do agree that USE_GTK and USE_GTK2 macros will make
> > the learning curve a bit less steep.
>
> Now, sure...but as new releases come out, should we add USE_GTK3,
> USE_GTK4...?  I think it scales better to have the one system that
> accepts a list of components rather than defining new macros everytime a
> new API release comes out.

If that is your actual concern, then let's define 'USE_GTK= 2', etc.
However, I don't think individual USE_GTK_FOO macros are all that hard to
manage.

My point here is simply that subsuming gtk under gnome forces non-gnome
ports to drive a screw with a jackhammer, and that type of design is
flawed from the start.

Doug

-- 

    This .signature sanitized for your protection


More information about the freebsd-ports mailing list