Re: Do not create conditional installation directories

2009-03-23 Thread Ralf Wildenhues
* Akim Demaille wrote on Thu, Mar 19, 2009 at 09:35:20PM CET: The confusion is that I am referring to the emptiness of the directory name (what I named an empty $(foodir)), while you are referring to an empty directory (what I named an empty $(foo_DATA)). I'm talking about

Re: Do not create conditional installation directories

2009-03-19 Thread Ralf Wildenhues
* Ralf Corsepius wrote on Thu, Mar 19, 2009 at 03:01:45PM CET: Ralf Wildenhues wrote: * Akim Demaille wrote on Wed, Mar 18, 2009 at 06:31:50PM CET: RW == Ralf Wildenhues ralf.wildenh...@gmx.de writes: But the question remains: how do you think we should address the bug

Re: Do not create conditional installation directories

2009-03-18 Thread Akim Demaille
RW == Ralf Wildenhues ralf.wildenh...@gmx.de writes: But the question remains: how do you think we should address the bug that bothers Akim, other than by this patch and a big warning in NEWS? My focus was more about an empty $(foodir), not an empty $(foo_DATA). I was suggesting that it

Re: Do not create conditional installation directories

2009-03-17 Thread Ralf Corsepius
Ralf Wildenhues wrote: * Ralf Corsepius wrote on Tue, Mar 17, 2009 at 12:08:44PM CET: Allan Caffee wrote: On Sun, 15 Mar 2009, Ralf Wildenhues wrote: There is another downside: up to now, one could use something like foo_DATA = to let $(DESTDIR)$(foodir) be created at

Do not create conditional installation directories

2009-03-15 Thread Ralf Wildenhues
the TODO item for the 'installdirs' target (yet). Do you still think it's worthwhile to have, and ok if we leave installdirs to be fixed in a later version? Thanks Akim for reminding me of this issue, Ralf Do not create conditional installation directories. TODO: doc If primaries