> 2007-01-01 Bruno Haible <[EMAIL PROTECTED]>
>
> * m4/canonicalize.m4 (AC_FUNC_CANONICALIZE_FILE_NAME): Remove
> PROVIDE_CANONICALIZE_FILENAME_MODE macro definition.
> * lib/canonicalize.h: Test GNULIB_CANONICALIZE instead of
> PROVIDE_CANONICALIZE_FILENAME_MODE.
I appl
Simon Josefsson wrote:
> > There are actually 3 ways to use gnulib:
> > 1) manual file copies, considering the contents of the module
> > descriptions,
> > 2) using a script based on the elementary --extract-... accessors of
> > gnulib-tool,
> > 3) using gnulib-tool --import.
>
> Do we
Bruno Haible <[EMAIL PROTECTED]> writes:
> There are actually 3 ways to use gnulib:
> 1) manual file copies, considering the contents of the module descriptions,
> 2) using a script based on the elementary --extract-... accessors of
> gnulib-tool,
> 3) using gnulib-tool --import.
Do we
Bruno Haible <[EMAIL PROTECTED]> wrote:
> I've now removed the "magic" from gnulib-tool's func_get_autoconf_snippet
> function, and instead created a gnulib-common.m4 that people not using
> gnulib-tool can use in their project.
Hi Bruno,
I'm glad you found a better way.
Now we can have our cake
Hello Jim,
> I'd rather defer this sort of change, since it introduces a hard
> dependency on gnulib-tool, with only marginal added value. With this
> sort of change, a project that uses this module without going through
> gnulib-tool will not work properly.
>
> If/once we all agree that it's ok
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Hi Jim,
>
> Now that gnulib-tool defines GNULIB_CANONICALIZE when the canonicalize module
> is in use, the PROVIDE_CANONICALIZE_FILENAME_MODE macro is redundant. Here is
> a proposed patch:
>
> 2007-01-01 Bruno Haible <[EMAIL PROTECTED]>
>
> * m4/ca
Hi Jim,
Now that gnulib-tool defines GNULIB_CANONICALIZE when the canonicalize module
is in use, the PROVIDE_CANONICALIZE_FILENAME_MODE macro is redundant. Here is
a proposed patch:
2007-01-01 Bruno Haible <[EMAIL PROTECTED]>
* m4/canonicalize.m4 (AC_FUNC_CANONICALIZE_FILE_NAME): Remov
