| 1 |
On Monday 05 November 2007, Mart Raudsepp wrote: |
| 2 |
> On E, 2007-11-05 at 16:19 +0100, Piotr Jaroszyński wrote: |
| 3 |
> > Hello, |
| 4 |
> > |
| 5 |
> > I think it's time to add a more general flag for enabling visibility |
| 6 |
> > support in packages as currently there is only a kde specific one |
| 7 |
> > (kdehiddenvisibility) and I don't think it makes sense to add a new one |
| 8 |
> > for each package that needs it. |
| 9 |
> |
| 10 |
> Why do they need it, is the question. If it's supported and stable, it |
| 11 |
> should just be enabled, end of story, in my opinion. I believe it was |
| 12 |
> optional in KDE due to it not being stable for some reason (either GCCs |
| 13 |
> at the time were sketchy or their build system problems weren't smoothed |
| 14 |
> out, I guess). |
| 15 |
> |
| 16 |
> > I have just added a local "visibility" flag for paludis and that's also |
| 17 |
> > my candidate for the global one, but better names are welcome. |
| 18 |
> |
| 19 |
> Why not enable it by default and unconditionally (other than GCC version |
| 20 |
> being used supporting it) in this specific case? |
| 21 |
|
| 22 |
this sounds good to me too ... binding USE flags to compiler options is |
| 23 |
generally frowned upon and we should avoid it when possible. |
| 24 |
-mike |
Archives