>
> consequently it shouldn't ship config.guess or config.sub either. these two
> cause frequently more trouble.
I do not see these files in CVS ???
> consequently it shouldn't expose automake-version specific behaviour by
> putting configure.in and configure.ac there. all automake versions can read
> configure.in, not all can read configure.ac. why there is a symlink is
> beyond me.
I guess most other questions answered Eugene so I'll just explaing this one.
Modern distribution like Debian allows to have both autoconf2.52 & autoconf2.13
to be present in the system. They are choosed according to the
extension of configure script - so if we want to process them with
new auto* we add symlinked configure.ac - if you have just old auto* installed
it will ignore linked configure.ac file so there is no problem.
> consequently it shouldn't put generated files in cvs and use hacks like
> touch to fix the dependencies again.
I guess you are talking about 2 month old version of CVS archive...
> > I've got autoconf 2.13 with automake 1.4 and it worked fine for me
> > ever since. Can't tell you about automake 1.5 for sure. As far as I
> > know they broke a lot of their compatibility with 1.4.
>
> Yes and no. Its for sure more strict and doesn't tolerate that many errors
> anymore.
new automake-1.5 really is incompatible - they have changed behaviour of
some basic variables and without any reason
- in Debian there are some 300 packages right now which have become
uncompilable - so I guess avifile is pretty good as it already works nicely...
(but you must have correctly installed system)
Otherwice you have to wait for CVS snapshot
--
.''`. Which fundamental human right do you want to give up today?
: :' : Debian GNU/Linux maintainer - www.debian.{org,cz}
`. `' Zdenek Kabelac kabi@{debian.org, users.sf.net, fi.muni.cz}
`- Resistance is futile. You all will be packaged
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
