RE: [Linphone-developers] head configure errors

[Kowalski, Francois-Xavier]

strk wrote:
> On Wed, Nov 15, 2006 at 11:48:05AM +0100, strk wrote:
>> On Wed, Nov 15, 2006 at 11:41:08AM +0100, Kowalski, Francois-Xavier
>> wrote: 
>> 
>>> FYI, the autotools team took care of this case.  Their basic advice
>>> -- documented in the info pages -- is to deliver in the source
>>> distribution the aclocal.m4 the maintainer generated when doing
>>> ./autogen.sh under the name acinclude.m4.
>> 
>> Interesting. Any online reference of this ?

Web-page of the info page
<http://www.ugcs.caltech.edu/manuals/devtool/automake-1.9.6/automake_28.html
>
<http://www.gnu.org/software/libtool/future.html>

> Actually, It is completely fine *not* to distribute the macros with
> releases, what I'm debating is wheter we should keep a copy of them
> in the CVS repository. Do autotools guys have an advice for this as
> well ?

I have undergone problems with another software (partysip) which uses
specific macros but does not deliver them: it is then un-possible to edit
the configure.in|ac or Makefile.am, because aclocal lacks the macros
definition.  Only ./configure is left possible.  That's a delivery choice:
do you want developpers to be able to do some development work based on
"make dist" output, or do you require them to hook to always hook to CVS.

If you go one step forward & remove the macros from the CVS, it will
developper's life even harder if they do not uwse the exact same distro as
yours.

My portability advice is: do not deliver the macros as-is, but rather as an
acinclude.m4, but let them into CVS.

--FiX

smime.p7s
Description: S/MIME cryptographic signature