bug#7988: the manual suggests installing macro files to hard-coded location

2011-10-01 Thread Stefano Lattarini
On Wednesday 28 September 2011, Stefano Lattarini wrote: > OK, now we have ACLOCAL_PATH support implemented into maint, so it's time to > fix this bug. I'll push the attached patch to maint in a couple of days if > there is no objection. > > Regards, > Stefano > Pushed now. I'm thus closing t

bug#7988: the manual suggests installing macro files to hard-coded location

2011-09-28 Thread Stefano Lattarini
On Sunday 20 March 2011, Peter Johansson wrote: > Hello Stefano, > > On 3/19/11 8:36 AM, Stefano Lattarini wrote: > > > > Another viable approach would be to install the third-party macro file > > in `$(third-party-prefix)/share/aclocal', and then extend the file > > `$(aclocal-prefix)/share/acloc

bug#7988: the manual suggests installing macro files to hard-coded location

2011-03-19 Thread Peter Johansson
Hello Stefano, On 3/19/11 8:36 AM, Stefano Lattarini wrote: On Saturday 05 February 2011, Peter Johansson wrote: I find the last sentence a bit strange because to me that sounds like Automake suggests that packagers should install macro files in a hard-coded directory not relative to $(prefix)

bug#7988: the manual suggests installing macro files to hard-coded location

2011-03-19 Thread Stefano Lattarini
On Saturday 05 February 2011, Peter Johansson wrote: > Hello, > Hello Peter, and sorry for the terrible delay. > In the manual, > http://sources.redhat.com/automake/automake.html#Invoking-aclocal, > I read about the `--print-ac-dir' option: > > ``Prints the name of the directory that aclocal wi

bug#7988: the manual suggests installing macro files to hard-coded location

2011-02-05 Thread Peter Johansson
Hello, In the manual, http://sources.redhat.com/automake/automake.html#Invoking-aclocal, I read about the `--print-ac-dir' option: Prints the name of the directory that | |aclocal will search to find third-party .m4 files. When this option is given, normal processing is suppressed. This optio