From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] C++ herd proposal
Date: Fri, 16 Sep 2005 18:20:57 -0400 [thread overview]
Message-ID: <432B4549.1070400@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4481 bytes --]
Since we currently have language herds for other languages such as Ada,
Perl, and Java, I don't think C++ should be any different. There are
currently many packages in the tree that are C++ libraries or utilities
that are no-herd and are actively maintained, and there are probably
some that have just been sitting around rotting. With the creation of a
C++ herd, there would be a team that could support these packages,
instead of a single maintainer, if the package has one. Below is a list
of all of the packages that I believe would qualify as falling under
this herd. If you see your name in the following list, I'd especially
like to hear from you. Names with a '?' next to them are packages that
had no metadata and I guessed from the changelog who the maintainer is.
I would also like to see many of them, if not all, moved to the dev-cpp
category:
dev-cpp/commoncpp2 (no-herd, arj)
dev-cpp/gccxml (no-herd, g2boojum)
dev-cpp/libibinio (no-herd, spock)
dev-cpp/poslib (no-herd, matsuu)
dev-cpp/rudiments (no-herd, matsuu)
dev-db/libodbc++ (no-herd, robbat2)
dev-libs/STLport (no-herd, vapier?)
dev-libs/asyncresolv (no-herd, jhhudso?)
dev-libs/blitz (no-herd, dragonheart)
dev-libs/boost (no-herd, morfic)
dev-libs/cgicc (no-herd, ka0ttic)
dev-libs/commonc++ (duplicate of dev-cpp/commoncpp2 as far as I
can tell, unmaintained?)
dev-libs/darts (no-herd, unmaintained?)
dev-libs/dvacm4 (no-herd, pvdabeel?)
dev-libs/dvcgi (no-herd, ka0ttic)
dev-libs/dvutil (no-herd, ka0ttic)
dev-libs/fampp2 (no-herd, vapier)
dev-libs/ferrisloki (no-herd, vapier)
dev-libs/ibpp (no-herd, sekretarz)
dev-libs/korelib (no-herd, george?)
dev-libs/libcoyotl (no-herd, aliz)
dev-libs/libevocosm (no-herd, aliz)
dev-libs/libferrisstreams (no-herd, vapier)
dev-libs/log4cpp (no-herd, george?)
dev-libs/log4cxx (no-herd, ka0ttic)
dev-libs/luabind (no-herd, rphillips)
dev-libs/ntl (no-herd, george?)
dev-libs/pcre++ (no-herd, eradicator)
dev-libs/ptypes (no-herd, dragonheart? george?)
dev-libs/quantlib (no-herd, vanquirius)
dev-libs/rlog (no-herd, vanquirius)
dev-libs/socketstream (no-herd, george? dragonheart?)
dev-libs/sucs (no-herd, ka0ttic)
dev-libs/swl (no-herd, trapni upstream dead? The site
appears to be dead)
dev-libs/wefts (no-herd, flameeyes)
dev-libs/xerces-c (no-herd, halcy0n)
dev-libs/xmlwrapp (no-herd, ka0ttic)
dev-libs/yaz++ (no-herd, robbat2)
dev-util/leaktracer (no-herd, svyatogor?)
net-libs/socket++ (no-herd, ka0ttic)
Possible candidates (most of these are for C and C++):
dev-libs/nana (no-herd, pyrania?)
dev-libs/xmlrpc-c (no-herd, jhhudso)
dev-libs/xxl (no-herd, ka0ttic)
dev-util/astyle (no-herd, karltk)
dev-util/bcpp (no-herd, chriswhite?)
dev-util/cccc (no-herd, dragonheart?)
dev-util/ccmalloc (no-herd, dholm)
dev-util/cdecl (no-herd, phosphan)
dev-util/cweb (no-herd, no one)
dev-util/flawfinder (no-herd, aliz?)
dev-util/rats (no-herd, robbat2)
Currently under another herd, but seems to make more sense here:
dev-cpp/libxmlpp (gnome-mm, ka0ttic)
dev-cpp/sptk (desktop-misc, iluxa?)
dev-libs/libsigc++ (gnome-mm, ka0ttic)
dev-libs/libsigcx (gnome-mm, ka0ttic)
dev-libs/mxmlplus (text-markup, usata)
dev-libs/xplc (net-dialup, mrness)
dev-util/cppunit (lang-misc, george?)
dev-util/qtunit (kde, centic?)
net-libs/wvstreams (net-dialup, mrness?)
I would like all of the current maintainers of these packages to keep
maintaining them, and they wouldn't be required to join the cpp team,
but there are a few people that seem to maintain quite a few C++
libraries that might be interested in joining.
If there is not a very good reason against the creation of this herd, I
would like to do so in the coming week. As for the name, cpp may be a
little misleading, any better suggestions? In the list above, I have
libraries for C++, as well as utilities.
Thanks,
Mark
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-09-16 22:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 22:20 Mark Loeser [this message]
2005-09-16 23:20 ` [gentoo-dev] [RFC] C++ herd proposal 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
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=432B4549.1070400@gentoo.org \
--to=halcy0n@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