use_gnomeng

[Adam Weinberger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> (04.20.2003 @ 1422 PST): Joe Marcus Clarke said, in 2.1K: <<
> > 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.

USE_ESOUND and USE_IMLIB should be taken out of bsd.gnome.mk and should
be excised from the ports tree stat, IMO.

> > 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.

Your point is well taken, except that the GTK libraries are ubiquitous
compared to any other GNOME components. I think that the relative
complexity of the USE_GNOME system as compared to "USE_GTK2=yes" is
warranted for all other GNOME components, but I wonder if the
extra-macros-to-support tradeoff is worth it for the relative ease of
porting apps that simply utilize the toolkit.

On the other hand, "USE_GNOME= gtk20" isn't all that difficult. I think
it may be worth it to add a paragraph towards the top of the docs I'm
hacking to spell out "If you want gtk2 libs, do this."

# Adam


- --
Adam Weinberger
vectors.cx	>>	adam at vectors.cx
FreeBSD.org	<<	adamw at FreeBSD.ORG
#vim:set ts=8: 8-char tabs prevent tooth decay.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+oxF0o8KM2ULHQ/0RAhl8AKDcf9XNpPQpK26GZ0HOsnoDn+Q5JQCeOfbk
5oZJA5+DR/ycQNHcWGbAUfo=
=x3pA
-----END PGP SIGNATURE-----