From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: new "qt" category
Date: Sun, 20 Jan 2013 16:39:55 +0800 [thread overview]
Message-ID: <CAB9SyzRUOXa0eT-7WN0_9xJ-Lgn32b57bHvJDWJdzxOaNv46fw@mail.gmail.com> (raw)
In-Reply-To: <kdg86f$4gq$1@ger.gmane.org>
On 20 January 2013 15:59, Nikos Chantziaras <realnc@gmail.com> wrote:
> Just a user with a suggestion here. Since portage already has kde-base and
> kde-misc, why not qt-base and qt-misc (and qt-something is the need arises.)
> Qt5 will have standard core modules and extensions. qt-base and qt-misc
> look like they can cover these.
There is no need for multiple qt categories. We want everything that
the upstream Qt Project considers to be part of the Qt Framework to be
in one category. Besides that there are only a handful of third-party
extensions, such as qwt. There is no need for a separate category for
those at this point in time.
--
Cheers,
Ben | yngwin
Gentoo developer
Gentoo Qt project lead, Gentoo Wiki admin
next prev parent reply other threads:[~2013-01-20 8:40 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 13:57 [gentoo-dev] RFC: new "qt" category Ben de Groot
2013-01-17 14:03 ` Ian Whyman
2013-01-17 14:05 ` Diego Elio Pettenò
2013-01-17 14:33 ` Ben de Groot
2013-01-17 14:45 ` Diego Elio Pettenò
2013-01-19 11:23 ` Ben de Groot
2013-01-17 16:51 ` Ciaran McCreesh
2013-01-17 17:05 ` James Cloos
2013-01-17 17:08 ` Ciaran McCreesh
2013-01-17 19:35 ` James Cloos
2013-01-17 19:44 ` Ciaran McCreesh
2013-01-18 4:24 ` Mike Frysinger
2013-01-18 15:13 ` Markos Chandras
2013-01-17 14:09 ` Chí-Thanh Christopher Nguyễn
2013-01-17 14:38 ` Ben de Groot
2013-01-17 14:11 ` Alexander Berntsen
2013-01-17 14:25 ` [gentoo-dev] " Michael Palimaka
2013-01-17 14:43 ` Alexander Berntsen
2013-01-17 14:30 ` [gentoo-dev] " vivo75
2013-01-17 14:43 ` Samuli Suominen
2013-01-17 15:57 ` Ulrich Mueller
2013-01-17 17:03 ` James Cloos
2013-01-17 17:14 ` Ciaran McCreesh
2013-01-17 17:52 ` Rich Freeman
2013-01-17 18:40 ` Chris Reffett
2013-01-17 22:32 ` Georg Rudoy
2013-01-17 22:46 ` Andreas K. Huettel
2013-01-17 22:57 ` Alec Warner
2013-01-18 19:16 ` Federico "fox" Scrinzi
2013-01-18 19:22 ` Christoph Junghans
2013-01-19 10:56 ` Ben de Groot
2013-01-19 12:43 ` Diego Elio Pettenò
2013-01-19 13:21 ` Rich Freeman
2013-01-19 13:39 ` Diego Elio Pettenò
2013-01-19 13:46 ` Patrick Lauer
2013-01-19 14:00 ` Rich Freeman
2013-01-19 14:14 ` Ben de Groot
2013-01-19 15:38 ` Michael Weber
2013-01-19 22:55 ` Francesco Riosa
2013-01-20 8:17 ` Ben de Groot
2013-01-19 16:48 ` [gentoo-dev] " Duncan
2013-01-20 8:24 ` Ben de Groot
2013-01-20 9:50 ` Duncan
2013-01-20 13:35 ` Dale
2013-01-20 13:59 ` Ben de Groot
2013-01-20 17:04 ` Duncan
2013-01-20 18:03 ` Dale
2013-01-19 21:03 ` [gentoo-dev] " Philip Webb
2013-01-20 8:29 ` Ben de Groot
2013-01-19 19:34 ` Ian Stakenvicius
2013-01-19 19:27 ` Ian Stakenvicius
2013-01-19 17:19 ` Michał Górny
2013-01-19 19:57 ` Markos Chandras
2013-01-19 22:59 ` Francesco Riosa
2013-01-20 8:34 ` Ben de Groot
2013-01-20 7:59 ` [gentoo-dev] " Nikos Chantziaras
2013-01-20 8:39 ` Ben de Groot [this message]
2013-01-20 9:09 ` Nikos Chantziaras
2013-01-20 9:20 ` Ben de Groot
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=CAB9SyzRUOXa0eT-7WN0_9xJ-Lgn32b57bHvJDWJdzxOaNv46fw@mail.gmail.com \
--to=yngwin@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