Re: [MinGW-dvlpr] RFC: FRS Structure for MinGW

[Keith M. <kei...@us...>]

On 14/11/11 12:33, Earnie wrote:
> Keith Marshall wrote:
>> On 13/11/11 17:45, Earnie wrote:
>>> Actually it just needs to be a file with README in the name.
>> 
>> And it's case agnostic.  Yeah, I knew that; readme.txt fits the bill,
>> doesn't it?  It's *generated* for mingw-get, in the same directory as
>> the README which goes in the source distribution, and I wanted to avoid
>> the potential README vs. readme conflict, which would arise for anyone
>> building on a case-insensitive platform, (such as MS-Windows).
> 
> Only if readme and README were in the same directory.

And, as I've said above, in the mingw-get case, they ARE: README and
readme.txt are both generated, into a common build directory, (and from
a common source, at least for part of the readme.txt content).  README
goes into the distributed source tarball; readme.txt is presented to
visitors to the download page, where it summarises content from all
three of README, NEWS and INSTALL.

> README is the GNU expected file.

So what?  1) We aren't constrained by GNU standards; 2) I'm providing
README anyway, where GNU mandates it, in the source tarball; 3) my
readme.txt is published ONLY on an SF web page, where again, GNU
standards are not applicable.

I'm NOT changing this, for mingw-get, just because you seem to have some
sort of hang-up about readme.txt as a name.  If you prefer to use README
as your name of choice, I'm not objecting, but do be aware that
MS-Windows knows that readme.txt can be opened by notepad.exe, in the
event that SF's former rendering problem should recur; it doesn't know
what to do with README.

-- 
Regards,
Keith.