PATCH: configure.in new firsttry

[Ali Akcaagac <ali akcaagac stud fh-wilhelmshaven de>]

hi,

in the attachment you receive my first try of a new
configure.in file that suits new autoconf, automake,
gettext and libtool and also the current way of GNOME

please note that this is more or less a usecase example
and show you how it should be done correctly. the current
configure.in is more a hack it doesnt work but i would
like to get help so we could get the new one running
and added to the cvs.

what changed.

a new directory named 'hacked-macros' got added which
includes some gnome relevant macros needed in the
configure.in file (almost all gnome RELEVANT core
programs, nautilus, galeon, devhelp and gnome itself
contains this dir). we should change nothing in this
directory. it gets automatically updated when cvs
updating.

autogen.sh got changed to the default new gnome autogen
file, this is around 2400-2500 bytes in lenght and solves
all kinda issues with recent configuration macros etc.
also simplifies certain tasks. its also in nearly all
other gnome packages. we need to change the 'project'
name. i've set that one to 'balsa' every app that uses
this set its project e.g. galeon to 'galeon' etc...
nothing else should be changed there.

confiure.in yes thats the tricky task. many things inside
are so what totally obsolete, redundant or just outdated.

the first 20 lines you see some first try of me to have
things correctly versioned and changed.

i would really appreciate someone helping me to get this
one better and running. but the CORRECT way. due the fact
of compatibility and the way gnome moves, we should use
gnome relevant macros and avoid using the default ones
to determine things. at least use the <application>-config
file to get all correct values.

please help thanks...

-- 
Name....: Ali Akcaagac
Status..: Student Of Computer & Economic Science
E-Mail..: mailto:ali.akcaagac@stud.fh-wilhelmshaven.de
WWW.....: http://www.fh-wilhelmshaven.de/~akcaagaa

balsa.tar.gz