2014-02-26 12:35 GMT+04:00 Dirkjan Ochtman <d...@gentoo.org>: > On Wed, Feb 26, 2014 at 9:26 AM, Georg Rudoy <0xd34df...@gmail.com> wrote: >> I'm currently considering using C++14 in my project, particularly >> features that aren't supported by gcc 4.8 and are barely supported by >> 4.9 [1], but the standard is already fully supported by clang 3.4 [2]. >> Thus I wonder how bad is actually depending on recent clang in >> ebuilds? > > If you want to do that, it's not a problem with me. That said, I > probably wouldn't install packages that wanted to pull in a whole > different toolchain unless I wanted them really badly (but on machines > where I already have clang installed, I might not even notice). > > I'd say there's value in staying close to where the community's at, if > you actually want your software to be used. If you don't care that > much about your software being used by other people, nobody can stop > you.
I thought about some policy-related problems. Good if there aren't any. Thanks for the opinion. Depending strictly on clang is more like a temporary measure until gcc catches up, which I hope will happen fast enough. In this case I'll also probably stick with just introducing the dependency in newer, probably even unpackaged modules so everyone will be able to use what's already considered to be somewhat stable and solid part of the app with "standard" gcc. -- Georg Rudoy
