Bug#431014: Why won't you ship /usr/bin/gcc-snapshot?
On 12/31/2011 01:34 AM, Vincent Lefevre wrote:
> On 2011-12-30 17:15:00 -0600, Jonathan Nieder wrote:
>> No, I mean that packagers can but should not use
>>
>> Build-Depends: gcc-snapshot
>>
>> CC = gcc-snapshot
>>
>> "Don't do that, then." you might say. But not providing a
>> /usr/bin/gcc-snapshot wrapper provides people with a reminder to look's
>> at README.Debian and not to do that.
>
> OK. Couldn't the wrapper detect that it is being used by a packager
> (e.g. because some environment variable is set by the build process)
> and output an error in such a case?
A wrapper will never remind you using the new library paths at runtime. The
snapshot package is meant to get early feedback about the development version of
GCC, either for a rebuild test, or to easily test for compiler errors on porter
boxes. It's not a package meant for regular development. I really prefer to
have users either set environment variables or create the wrapper scripts on
their own.
Reply to: