Re: License change

On 2007-05-10, Matti Bickel <[email protected]> wrote:
> While i recognize the fact, that --as-needed doesn't (and probably never
> will) catch up with some of it's use cases, i see no point in denying a
> "fix" for a broken --as-needed, even if it's not against the ld or gcc
> codebase.

I didn't say that. I just said that the flag should be fixed rather
than keeping such workarounds there forever.

> The message will use elog, which is user configurable and some of our
> users have it mail them the output. In one case, namely the paludis
> package manager, elog messages get shown at the end of the complete
> batch build. In every case, the user gets a log file with the messages
> the package emitted.
>
> The use flags will have a (unsupported upstream) added to their
> description.

I don't think that's quite prominent enough. Also "unsupported 
upstream" doesn't have quite right the connotation: it could
be mistaken that the particular feature is not supported. 
The words "upstream support void" would perhaps be more to the
effect. There's also the problem of users getting instructions
from elsewhere, and never reading the description, or the log.
Therefore, the flags themselves should perhaps be prefixed
"support-void"; cmp. "warranty void" stickers on devices. 
(For FOSS there's no warranty, of course.)

-- 
Tuomo