On 04/03/2012 10:05 PM, Stefano Lattarini wrote:
On 04/03/2012 10:04 PM, Stefano Lattarini wrote:
OK, you've all made clear you have your sensible reasons to have the '.info'
files generated in the builddir in your use cases. Since the actual change
required by automake to allow this is very
On 04/03/2012 10:04 PM, Stefano Lattarini wrote:
OK, you've all made clear you have your sensible reasons to have the '.info'
files generated in the builddir in your use cases. Since the actual change
required by automake to allow this is very small and safe, I'm ready to do
it (see attached
OK, you've all made clear you have your sensible reasons to have the '.info'
files generated in the builddir in your use cases. Since the actual change
required by automake to allow this is very small and safe, I'm ready to do
it (see attached patch, which I will push in a couple of days to
Stefano == Stefano Lattarini stefano.lattar...@gmail.com writes:
Stefano On a second though, by double-checking the existing code, I
Stefano couldn't see how the 'cygnus' option could possibly influence
Stefano the location of the generated info files -- and it turned out
Stefano it didn't!
Stefano Lattarini stefano.lattar...@gmail.com writes:
But since I'm not yet ready to publish this new feature, I intend to make
it available only though the new, undocumented option named (literally)
hack!info-in-builddir. I hope this is acceptable to you.
Sure, works for me.
Thanks.
Ian
On 04/03/2012 09:04 PM, Stefano Lattarini wrote:
OK, you've all made clear you have your sensible reasons to have the '.info'
...
it available only though the new, undocumented option named (literally)
hack!info-in-builddir. I hope this is acceptable to you.
...
*undocumented* option
Pedro Alves pal...@redhat.com writes:
OK, you've all made clear you have your sensible reasons to have the '.info'
...
it available only though the new, undocumented option named (literally)
hack!info-in-builddir. I hope this is acceptable to you.
...
*undocumented* option
