From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation
Date: Fri, 27 May 2016 13:55:41 -0400 [thread overview]
Message-ID: <0e8fb805-1a94-bd83-a194-b642b1e5ba50@gentoo.org> (raw)
In-Reply-To: <20160527174420.GA10125@whubbs1.gaikai.biz>
On 5/27/16 1:44 PM, William Hubbs wrote:
> On Fri, May 27, 2016 at 01:14:17PM -0400, Anthony G. Basile wrote:
>> On 5/27/16 12:59 PM, rindeal wrote:
>>> On 27 May 2016 at 18:54, landis blackwell <blackwelllandis@gmail.com> wrote:
>>>> I stopped reading after you reminded me it was 2016
>>>
>>> Good to know, thanks for stopping by.
>>>
>>
>> Yeah the "its <current> year" meme has been making its rounds of the
>> internet.
>>
>> anyhow, my 2017 question is about avahi. right now i have USE=gtk and
>> gtk3, where gtk really means gtk2. i'm not going to change that because
>> it fits QA's specs. but i could remove it altogether and just drop gtk2
>> support for the next release. good idea? bad idea? i guess i'm asking
>> whats the status of gtk2 in gentoo seeing as its dead upstream.
>
> From QA's pov, the gtk2 support is up to you, but I also would recommend
> adding a gtk2 use flag if you keep it around. The idea is to eventually
> get away from the non-versioned use flag.
It wouldn't be adding, it would be renaming a flag which is possible but
annoying. Anyhow I'll cross that bridge after the next release of avahi.
>
> Thanks,
>
> William
>
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2016-05-27 17:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:21 [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation Mart Raudsepp
2016-05-27 15:02 ` Brian Dolbec
2016-05-27 16:35 ` Canek Peláez Valdés
2016-05-27 17:17 ` Brian Dolbec
2016-05-27 15:34 ` Ian Stakenvicius
2016-05-27 15:40 ` William Hubbs
2016-05-27 17:28 ` rindeal
2016-05-27 18:23 ` M. J. Everitt
2016-05-27 21:22 ` NP-Hardass
2016-05-27 15:56 ` Patrick Lauer
2016-05-27 16:15 ` Austin English
2016-05-27 16:54 ` landis blackwell
2016-05-27 16:59 ` rindeal
2016-05-27 17:14 ` Anthony G. Basile
2016-05-27 17:44 ` William Hubbs
2016-05-27 17:55 ` Anthony G. Basile [this message]
2016-05-27 21:09 ` William Hubbs
2016-05-27 18:23 ` Mart Raudsepp
2016-05-27 18:28 ` Ian Stakenvicius
2016-05-27 19:06 ` Daniel Campbell
2016-05-30 15:17 ` Mart Raudsepp
2016-05-27 18:10 ` waltdnes
2016-05-27 18:26 ` Mart Raudsepp
2016-05-27 18:44 ` rindeal
2016-05-27 18:51 ` [gentoo-dev] [RFC] improper use of X Ian Stakenvicius
2016-05-27 18:57 ` [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation Daniel Campbell
2016-05-27 21:45 ` NP-Hardass
2016-05-27 22:05 ` Daniel Campbell
2016-05-27 22:21 ` NP-Hardass
2016-05-30 20:46 ` Joakim Tjernlund
2016-06-06 15:37 ` NP-Hardass
2016-05-27 21:08 ` NP-Hardass
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=0e8fb805-1a94-bd83-a194-b642b1e5ba50@gentoo.org \
--to=blueness@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