James Carlson wrote:
> George Vasick writes:
>> Thanks for your many comments and helpful feedback. Attached, please
>> find a revised proposal. It contains major changes to the previous
>> proposal as follows:
>
> This looks pretty nice except for one bit that seems a little
> unfortunate:
>
>> usr/bin/cpp=./cpp-4.3.2
>
> That's an awfully generic name to be camping out on, especially with
> the existing /usr/lib/cpp, *and* with a cpp(1) man page delivered as
> part of the system. This seems quite likely to me to lead to future
> problems -- such as ./configure-like scripts (and users!) mistakenly
> detecting one but not the other.
>
> No, before you ask, I don't have a good solution for it in mind.
I noticed this potential issue as well. There were two factors in my
proposal to leave the Gnu version /usr/bin/cpp:
1) According to the /usr/lib/cpp man page, the preferred way to invoke
/usr/lib/cpp is via the cc command rather than invoking it directly.
2) Section 2.4, 'g' prefixing, of PSARC/2007/047, /usr/gnu, says
GNU components that do not conflict with existing or anticipated
components in the system's default commands environment should not
be placed in /usr/gnu, and do not require 'g'-prefixing.
I felt that applied here and proposed to leave the Gnu /usr/bin/cpp as is.
Thanks,
George
