public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Announcement of The G Palmtop Environment ebuilds
Date: Tue, 3 Feb 2009 11:47:15 -0800	[thread overview]
Message-ID: <20090203194715.GB3819@comet> (raw)
In-Reply-To: <20090203192431.GA3819@comet>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

On 11:24 Tue 03 Feb     , Donnie Berkholz wrote:
> > We currently provide an eclass and ebuilds arranged by top level
> > categories following upstream categorization. Explicitly gpe.eclass and
> > top level gpe-base gpe-net gpe-pim gpe-games gpe-utils gpe-media
> > gpe-xsession.
> > We know we have a lot of them but upstream finds useful to classify them
> > like that and so do we.
> 
> Could you expand on how each new category is useful?
> 
> > The eclass and some ebuilds were based on bugzie #101393. We started
> > playing with them as big flat gpe-base category which evolved over time
> > by means of consecutive testing on ARMv5 handheld devices and needs.
> > 
> > Since we are maintaining this over half a year now, we think that its
> > time to finally starting moving step-by-step the GPE suite into the
> > portage tree - starting with the eclass and toplevel categories.
> 
> What are the stats on package count per category?

I got this from solar:

     30 gpe-base
      8 gpe-games
      4 gpe-media
      9 gpe-misc
      2 gpe-net
     32 gpe-phone
      6 gpe-pim
     18 gpe-utils
      8 gpe-xsession

Unless those tiny ones are going to be growing a lot, I'm not terribly 
convinced of this many new ones.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-03 19:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 15:34 [gentoo-dev] Announcement of The G Palmtop Environment ebuilds Angelo Arrifano
2009-02-03 16:28 ` Richard Freeman
2009-02-03 17:10   ` Angelo Arrifano
2009-02-03 18:48     ` Ned Ludd
2009-02-03 18:54       ` Richard Freeman
2009-02-03 19:24 ` Donnie Berkholz
2009-02-03 19:47   ` Donnie Berkholz [this message]
2009-02-03 20:13     ` Angelo Arrifano
2009-02-03 20:20       ` Ciaran McCreesh
2009-02-03 21:37       ` [gentoo-dev] " Duncan
2009-02-04 11:56 ` [gentoo-dev] " Petteri Räty
2009-02-04 14:03   ` Angelo Arrifano
2009-02-04 16:36     ` Petteri Räty
2009-02-05  0:37       ` Angelo Arrifano
2009-02-05  0:51         ` Ned Ludd
2009-02-05  0:52         ` Petteri Räty
2009-02-07 21:05           ` Angelo Arrifano
2009-02-08 21:38             ` Petteri Räty
2009-02-05 20:21       ` [gentoo-dev] " Ryan Hill
2009-02-05 21:17         ` Petteri Räty

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=20090203194715.GB3819@comet \
    --to=dberkholz@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