Re: [gentoo-dev] Global useflag for enabling visibility support
On E, 2007-11-05 at 16:19 +0100, Piotr Jaroszyński wrote: Hello, I think it's time to add a more general flag for enabling visibility support in packages as currently there is only a kde specific one (kdehiddenvisibility) and I don't think it makes sense to add a new one for each package that needs it. Why do they need it, is the question. If it's supported and stable, it should just be enabled, end of story, in my opinion. I believe it was optional in KDE due to it not being stable for some reason (either GCCs at the time were sketchy or their build system problems weren't smoothed out, I guess). I have just added a local visibility flag for paludis and that's also my candidate for the global one, but better names are welcome. Why not enable it by default and unconditionally (other than GCC version being used supporting it) in this specific case? -- Mart Raudsepp Gentoo Developer Mail: [EMAIL PROTECTED] Weblog: http://planet.gentoo.org/developers/leio signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Global useflag for enabling visibility support
Piotr Jaroszyński [EMAIL PROTECTED] writes: I think it's time to add a more general flag for enabling visibility support in packages as currently there is only a kde specific one (kdehiddenvisibility) and I don't think it makes sense to add a new one for each package that needs it. Some packages, such as mozilla-firefox, enable visibility support without the use of a USE flag. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] Global useflag for enabling visibility support
On Monday 05 November 2007, Mart Raudsepp wrote: On E, 2007-11-05 at 16:19 +0100, Piotr Jaroszyński wrote: Hello, I think it's time to add a more general flag for enabling visibility support in packages as currently there is only a kde specific one (kdehiddenvisibility) and I don't think it makes sense to add a new one for each package that needs it. Why do they need it, is the question. If it's supported and stable, it should just be enabled, end of story, in my opinion. I believe it was optional in KDE due to it not being stable for some reason (either GCCs at the time were sketchy or their build system problems weren't smoothed out, I guess). I have just added a local visibility flag for paludis and that's also my candidate for the global one, but better names are welcome. Why not enable it by default and unconditionally (other than GCC version being used supporting it) in this specific case? this sounds good to me too ... binding USE flags to compiler options is generally frowned upon and we should avoid it when possible. -mike signature.asc Description: This is a digitally signed message part.
