public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markus Bertheau <twanger@bluetwanger.de>
To: tberman@gentoo.org
Cc: Georgi Georgiev <chutz-dated-1059395778.939403d6d488@gg3.net>,
	gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Categorization [was: app-cvs]
Date: 15 Jul 2003 17:13:37 +0200	[thread overview]
Message-ID: <1058282017.2635.15.camel@saphir> (raw)
In-Reply-To: <1058189075.12265.3.camel@phaze>

В Пнд, 14.07.2003, в 15:24, Todd Berman пишет:
> Just in general, app-cvs is a 'BAD' idea.
> 
> It defeats the *entire* purpose of what is going on in general.
> 
> In general, baring notable exceptions (gaim-cvs, private live-cvs pull
> ebuilds) I dont think live-cvs ebuilds are a good idea at all, and
> surely not a sound reason to add a category just for their use.
> 
Also as a related issue packages can be categorized in many ways and
often packages would belong to more that one category. To be consistent
we should use the same "categorization scheme" for every package. An
example:

nurbs++ is a C++ library, and it's in media-libs, I'm totally fine with
that. Then we have libxmlpp, which is a C++ wrapper to the C libxml (I
think), in dev-cpp. Given that I find nurbs++ in media-libs, I'd expect
to find libxmlpp in dev-libs. We don't put nurbs++ in dev-cpp just
because it's a C++ library.

Now the difference between nurbs++ and libxmlpp is, that libxmlpp is a
C++ wrapper, and nurbs++ is not, it's "natively" C++. But in my opinion
that doesn't justify putting it in a "C++ libraries" directory. After
all I don't think "Hmm, I'm writing a C++ application, let's look in
dev-cpp what library I could use", but rather "Hmm, I'm writing a
multimedia application, let's look in media-libs if there's already a
library doing half of my work".

-- 
Markus Bertheau.
Berlin, Berlin.
Germany.

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-07-15 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14  9:25 [gentoo-dev] app-cvs Tal Peer
2003-07-14  9:26 ` FRLinux
2003-07-14  9:40 ` Michele Balistreri
2003-07-14 10:24 ` Svyatogor
2003-07-14 10:42 ` rob holland
2003-07-14 11:12   ` Luca Barbato
2003-07-14 11:49     ` Michele Balistreri
2003-07-14 11:41 ` Dhruba Bandopadhyay
2003-07-14 11:18   ` Patrick Kursawe
2003-07-14 12:36   ` Georgi Georgiev
2003-07-14 13:24     ` Todd Berman
2003-07-14 17:55       ` Paul de Vrieze
2003-07-15 15:13       ` Markus Bertheau [this message]
2003-07-15 18:56 ` Dan Armak
2003-07-15  7:23   ` Alvaro Figueroa Cabezas
2003-07-17 13:31   ` Michael Andrews
2003-07-19  2:41 ` James H. Cloos Jr.

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=1058282017.2635.15.camel@saphir \
    --to=twanger@bluetwanger.de \
    --cc=chutz-dated-1059395778.939403d6d488@gg3.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=tberman@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