From: Christian Parpart <trapni@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] C++ herd proposal
Date: Sun, 18 Sep 2005 23:46:56 +0200 [thread overview]
Message-ID: <200509182346.58832.trapni@gentoo.org> (raw)
In-Reply-To: <200509171614.38174.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
On Saturday 17 September 2005 22:14, Mike Frysinger wrote:
> On Saturday 17 September 2005 02:22 pm, Mark Loeser wrote:
> > Kevin F. Quinn wrote:
> > >> I would also like to see many of them, if not all, moved to the
> > >> dev-cpp category:
> > >
> > > Is this bit really necessary?
> >
> > The reason for me adding that bit is the metadata from dev-cpp:
> >
> > The dev-cpp category contains libraries and utilities relevant to the
> > c++ programming language.
> >
> > Now to me, that means I can find *all* relevant C++ stuff here. If we
> > don't want that to be the case, maybe we should say "miscellaneous", but
> > why should something be in dev-libs, as compared with dev-cpp?
> > net-libs, I could understand, and dev-games, as those could be argued to
> > have a direct relation.
>
> for generic C++ packages (STLport/boost for example), i can see them being
> in the dev-cpp category ... but for packages which have specific uses
> already and arent in 'generic' categories, i dont think they should be
> moved -mike
if I do understand you correctly, I'd even not use dev-cpp as category,
instead something that contains the word `platform` or `framework` in it, as
STLport/boost/STL(libstdc++-v3,...) and others are exactly of that kind.
However, we've some more no-herd'ed packages to put into this new potential
c++ herd - but these are two different discussions/threads IMHO.
Regards,
Christian Parpart.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-09-18 20:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 22:20 [gentoo-dev] [RFC] C++ herd proposal Mark Loeser
2005-09-16 23:20 ` Mike Frysinger
2005-09-17 11:31 ` Christian Parpart
2005-09-17 1:34 ` Aaron Walker
2005-09-17 1:45 ` Ciaran McCreesh
2005-09-17 7:00 ` Robin H. Johnson
2005-09-17 9:36 ` Kevin F. Quinn
2005-09-17 11:33 ` Christian Parpart
2005-09-17 12:01 ` Kevin F. Quinn
2005-09-17 13:27 ` Christian Parpart
2005-09-17 18:22 ` Mark Loeser
2005-09-17 20:14 ` Mike Frysinger
2005-09-17 20:24 ` Mark Loeser
2005-09-19 9:43 ` Paul de Vrieze
2005-09-19 12:33 ` Mark Loeser
2005-09-19 13:22 ` warnera6
2005-09-20 5:21 ` Christian Parpart
2005-09-20 5:37 ` Georgi Georgiev
2005-09-20 6:37 ` Alin Nastac
2005-09-20 6:43 ` Georgi Georgiev
2005-09-20 7:01 ` Alin Nastac
2005-09-20 7:42 ` Brian Harring
2005-09-20 6:54 ` Kevin F. Quinn
2005-09-20 9:09 ` Martin Schlemmer
2005-09-20 16:32 ` Donnie Berkholz
2005-09-18 21:46 ` Christian Parpart [this message]
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=200509182346.58832.trapni@gentoo.org \
--to=trapni@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