Index: [thread] [date] [subject] [author]
  From: Jon M. Taylor <taylorj@ecs.csus.edu>
  To  : ggi-develop@eskimo.com
  Date: Sun, 19 Jul 1998 17:18:14 -0700 (PDT)

Re: libggi dependencies

On Sat, 18 Jul 1998, Jan Kneschke wrote:

> 
> On Sat, 18 Jul 1998, MenTaLguY wrote:
> 
> > On Fri, 17 Jul 1998, Jan Kneschke wrote:
> > 
> > > what about the automake/autoconf/...-package ?? the kde-project is using it
> > > all over the place on different archs and you i think you know the size of
> > > the kde-project.
> > 
> > Simple. auto* won't fly on *BSD.  autoconf requires GNU m4 to build
> > configure from the configure.in (not a problem for joe blow installing user,
> > who doesn't need to modify configure.in, but it is an issue for developers).
> > Most of the BSD folks I've talked to were quite upset about the possibility
> > of being required to install GNU tools just to do GGI development.

	What a surprise.
 
> ??? very tolerant i think. these developers should rename their 'make world'
> to 'make my_fine_bsd_world'. 
> where is the problem in using gnu-tools ?? 
> is it just a religious one or a functional ?

	This is absurd.  I have no problem accomodating those who do not
wish to switch shells, C compilers, make utils or other such fundamental
tools.  I have a BIG problem with people who will not install a very
useful tool that does not disturb their existing environment.  autoconf is
THE standard way to implement cross-platform-Unix building and installing
of source packages, and I'll be damned if I'll accept junking it just so
that someone does not have to run any GNU stuff on their system.  And of
course THEY won't be the ones to spend time hacking together a substitute,
right?  What nerve!

Jon


---
'Cloning and the reprogramming of DNA is the first serious step in 
becoming one with God.'
	- Scientist G. Richard Seed

Index: [thread] [date] [subject] [author]