This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Fix INSTALL description for modified files in source dir
On Fri, May 18, 2012 at 12:33 PM, Pedro Alves <palves@redhat.com> wrote:
> On 05/18/2012 05:28 PM, Carlos O'Donell wrote:
>
>> On Fri, May 18, 2012 at 12:13 PM, Pedro Alves <palves@redhat.com> wrote:
>
>>>> The manual should represent reality. I agree that we should file bug
>
>>>> reports, but that's orthogonal to the issue of documentation being
>>>> accurate. Do you agree?
>>>
>>> I agree, though mentioning the autom4te.cache directory doesn't sound useful
>>> for the target audience this documented is aims at. ?IIUC from the
>>> irc discussion, it's a side product of an autoconf check for working
>>> autoconf. ?Knowing where the .mo files end up sounds useful though.
>>
>> Who do you consider the intended audience of the document?
>
> It's the INSTALL file, so the subset of users that build and install
> glibc, system integrators, not core developers.
>
> Who do you consider would be interested in knowing that
> an autom4te.cache directory is created in the src dir?
You've convinced me.
Listing explicitly which directories or files are touched is not
useful given the audience, and possibly confusing.
Such an audience would only care to know that the source directory
must not be read-only.
Thus all we need to say is:
Please note that even though you're building in a separate build
directory, the compilation may need to create or modify files and
directories in the source directory.
Andreas, What do you think? Would you please file bugs to fix this too?
Cheers,
Carlos.