On Sun, Sep 20, 2015 at 9:27 AM, Manuel Rüger <mr...@gentoo.org> wrote:
> On 19.09.2015 23:04, hasufell wrote:
>> Friends,
>>
>> I think it is time to import LibreSSL[0]. There are not many packages
>> left that don't compile OOTB and those can be patched (e.g. dev-lang/ruby).
>>
>> My idea would be:
>>
>> 1. import "dev-libs/libressl" (this will block dev-libs/openssl) and
>> introduce the global USE flag "libressl" with the following description:
>> """
>> libressl - Use dev-libs/libressl as SSL provider (might need ssl USE
>> flag), packages should not depend on this USE flag
>> """
>>
>
> Devmanual says to discuss global useflags here before introducing them.
> IMO merely announcing them is not enough. See
> 288d8cd90fca12fafd021d86837851d8cb5c6efe.
>

++

I'm not hostile to the proposed plan, but you should at least allow a
few days for things to settle down if we're not talking about security
patches/etc.

This isn't directed at anybody in particular, but I've been noticing a
bit of a recent trend towards wanting to discuss a change at all ==
bikeshedding for years -> time to pout and threaten to walk out.  It
isn't really helpful.  Gentoo is a fairly large project - this isn't
some little community of 5 developers who chat at the bar and then go
write their code.

Discussing change serves many purposes:
1.  It provides notice of the change.
2.  It is possible that others will notice something the authors missed.
3.  It provides an opportunity for education.  The way junior
contributors become senior contributors is by interacting with those
doing changes.  That might mean making well-intentioned suggestions
that don't work.

SSL is pretty important, and over time I could see this becoming
bigger than kerberos/ffmpeg/etc.  It makes sense to at least give this
change some thought.  My concern with holding it up is that we don't
actually have a practical alternative that we can implement today, at
least not that I'm aware of.  So, I'm more inclined to just let this
move forward and let somebody with a grandiose plan for managing
symbol collisions/etc to demonstrate it before holding everything else
up.  But, if people have plans that work in either the short- or
long-term please speak up.

-- 
Rich

Reply via email to