[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gEDA-dev: Re: [Gnucap-devel] Gnucap docs build failure on FC5(and other places)



Sorry for not responding sooner.  I was on vacation, with no web 
access.

On Sunday 30 July 2006 10:28, Dan McMahill wrote:
> So, why all the recent problems?  It is because the recent
> snapshot distfile was not created using the current build
> system and hence there was a mismatch between what the build
> system is supposed to do and what files were actually
> shipped.  Also it seems that a couple of Makefile.am's have
> gotten slightly out of date. I'll be posting a patch to the
> gnucap list for that.

It is because there is a completely new build system that has 
not been tested adequately.  That's what you get in 
a "development snapshot".   

You can use the old system by typing "./configure.old" instead 
of "./configure".  It is my policy that when a major component 
is being replaced, and is perceived as being high risk, I carry 
the old one so you can revert to it when the new doesn't work.  
After the new system is proven to be superior, the old one is 
removed.

Both systems worked for me in my test systems.  (Primarily 
Debian, also Fedora-5, Ubuntu, Slackware, and Mac.)  Some of 
these do not have latex installed.  It didn't die for me.  It 
just gave the message and moved on.

The two systems are completely incompatible.  If you give up on 
one, start fresh with the other.  Some features work only with 
one.  Some work only with the other.  Regression testing, 
archive (RCS) management, and automated bug tracing work only 
with the old system, so I still consider the old system to be 
the primary development version.

Actually, the old ./configure script  (now ./configure.old) is a 
hack to make the old system work in an environment designed for 
autoconf.  The intent was to have a system wide config file, so 
all that was necessary was "make".  For years, I distributed 
a "./configure" script that did nothing at all.

There is a real need for a high quality replacement for 
autoconf.  



_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev