public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Global useflag for enabling visibility support
Date: Mon, 5 Nov 2007 16:13:30 -0400	[thread overview]
Message-ID: <200711051513.30798.vapier@gentoo.org> (raw)
In-Reply-To: <1194276334.28930.2.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2007-11-05 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 15:19 [gentoo-dev] Global useflag for enabling visibility support Piotr Jaroszyński
2007-11-05 15:25 ` Mart Raudsepp
2007-11-05 20:13   ` Mike Frysinger [this message]
2007-11-05 15:54 ` Graham Murray

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200711051513.30798.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox