Re: gEDA: Hold off on next release?

[Ales Hvezda <ahvezda-at-NOSPAMseul_dot_org>]

Hi Stuart,

[snip]
>I have gotten my system functional again.  The problem was that
>autogen wasn't finding certain m4 files (pkg.m4, gettext.m4, and
>guile.m4) when running the autotools.  I don't know why this
>happened since it used to work.  Anyway, I fixed the problem by
>incorporating these m4 files into the m4 directories of certain source


	I'm not particularly thrilled with including these m4 files in CVS
since on a working (whatever that is) system it "just works".  I'm worried
about version skew between what is in CVS and what is on local developers
machines.  I can pretty much guarantee that my version of gettext is
different than the m4 files in CVS.  However, I'm going to leave these
changes in CVS for now.

Hmmm.. How was it failing before you checked in these files?  Quite
curious.  I think a better way of testing intermediary snapshots on "real"
systems is to make the tarballs using "make dist" and install those.


>trees (libgeda, gschem, gnetlist, and geda IIRC).  I also munged
>around with a few other build files.  For example, I had to explicitly
>include @GUILE_LDFLAGS@ into a couple of "Makefile.am"s.  None of this
>should cause grief for anybody else.  Indeed, it is probably good
>since it will make gEDA/gaf's CVS more portable. 

	Hmmm.  Also curious why this was necessary since 

pkg-config libgeda --cflags --libs

	should include all the necessary libraries to link.

>
>Anyway, I have made all my changes to CVS.  Please go ahead and
>release when ready.

	Great.  It'll take me a few days to get back in the swing of
things after my holiday.

>
>BTW:  I'll let you decide what to do with Matthias' patches.  They
>look reasonable to me.

	Yeah, I'll probably commit those as well. Thanks.

								-Ales