Re: *_DATA containing blanks

[Ralf Corsepius]

On Thu, 2003-07-24 at 12:28, Alexandre Duret-Lutz wrote:
> [...]
> 
>  Ralf> Who needs java ? ;-)
> 
> I have to admit java is not really my cup of tea.
> 
> [...]
> 
>  Ralf> the actual origin of the problems is elsewhere.
> 
> Hmmm... let me guess... Unix?
No, ... automake ... ;-)

I can't deny the feeling that automake has sacrificed shell quoting to
accommodate java ;-)

>  Ralf> Just a thought: Don't automake parse the contents of make-variables? 
>  Ralf> Why doesn't it expand these variables and use expanded loops instead of
>  Ralf> trying to use these vars directly? This would also give automake the
>  Ralf> opportunity to quote sick vars (like those using $ or ' ') correctly?
> 
> Not for AC_SUBST variables :(
??? 

I had been referring to automake variables (EXTRA_DIST and *_DATA in
Makefile.ams).

Yes, they can contain autoconf substitions (@foo@), refer to
make-variables ($(foo)) and can be implicitly generated by automake (eg.
DISTFILES). But I don't see why automake can't parse them and expand all
fixed values (*_DATA = foo).

>  Ralf> For the moment, I'll give in and have to conclude that automake is not
>  Ralf> applicable to my problem.
> 
> At least not _DATA.   If you have only a few files, you may find
> to fragment of hope in install-data-local and distdir-hook?
distdir-hook doesn't seem to exist, dist-hook seems to be applicable to
work-around my problem.

However, this forces me to rely on automake internals ($distdir) and
results into such kind of pretty unpleasant Makefile.ams:

EXTRA_DIST = java$$sickness

dist-hook:
        cp -p $(srcdir)/foo\ 1 $(distdir)/foo\ 1

install-data-local:
        $(mkinstalldirs) $(DESTDIR)$(datadir)
        $(INSTALL_DATA) $(srcdir)/foo\ 1 $(DESTDIR)$(datadir)/foo\ 1

uninstall-local:
        rm -f $(DESTDIR)$(datadir)/foo\ 1

Ralf