should an empty "pkgdata_DATA" cause creation of $(pkgdatadir) by "make install"? (was: Re: [PATCH] gnulib-tool: fix imprecise comments)

[CC:ing Ralf, as I'd like to hear his opinion here] Reference: On 03/13/2012 01:14 PM, Stefano Lattarini wrote: > > Now that I think about it, I'm not sure whether it was done "by design" from > the beginning, > And I also miss

Re: should an empty "pkgdata_DATA" cause creation of $(pkgdatadir) by "make install"?

On 03/13/12 07:30, Stefano Lattarini wrote: [CC:ing Ralf, as I'd like to hear his opinion here] Reference: On 03/13/2012 01:14 PM, Stefano Lattarini wrote: Now that I think about it, I'm not sure whether it was done "by de

Re: should an empty "pkgdata_DATA" cause creation of $(pkgdatadir) by "make install"?

On 03/13/2012 08:55 AM, Robert Boehne wrote: >> >> So we're in a sort of a tie here: some users think that the current >> Automake >> behaviour is a feature (and I lean toward that position), other ones >> (with >> Ralf among them, apparently) believe it's a bug. Hmmm. What now? >> >> Regards, >>

Re: should an empty "pkgdata_DATA" cause creation of $(pkgdatadir) by "make install"? (was: Re: [PATCH] gnulib-tool: fix imprecise comments)

[Dropping bug-gnulib from CC.] Stefano Lattarini wrote: > So we're in a sort of a tie here: some users think that the current Automake > behaviour is a feature (and I lean toward that position), other ones (with > Ralf among them, apparently) believe it's a bug. Hmmm. The most important question

Re: should an empty "pkgdata_DATA" cause creation of $(pkgdatadir) by "make install"? (was: Re: [PATCH] gnulib-tool: fix imprecise comments)

On Tue, 13 Mar 2012, Bruno Haible wrote: Answer: For users who generate their Makefile.am (like gnulib-tool), yes. For users who use constructs like pkgdata_DATA = if WINDOWS pkgdata_DATA += documentation.chm endif if MACOS pkgdata_DATA += bundle.n