public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Angelo Arrifano <miknix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Donnie Berkholz <dberkholz@gentoo.org>
Subject: Re: [gentoo-dev] Announcement of The G Palmtop Environment ebuilds
Date: Tue, 03 Feb 2009 20:13:15 +0000	[thread overview]
Message-ID: <1233691996.22368.25.camel@localhost> (raw)
In-Reply-To: <20090203194715.GB3819@comet>

On Ter, 2009-02-03 at 11:47 -0800, Donnie Berkholz wrote:
> 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?

In my maintainer point of view, it just make sense to follow upstream
categorization of packages.

In the user centric view, it will be a lot more easier to know what
package is for by looking at each category.
gpe-xxxx is intended for embedded devices, one might want to keep it
clean and minimal.

> > 
> > > 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.
> 

They won't grow much over time so I understand your point.
Although, I would like to ask the drawbacks of adding those new
categories to portage.
Adding confusion and mess won't be an issue because these are very
specific categories which won't affect other ebuilds or other
categories.
After all we don't want to introduce something like dev-gpe mail-gpe
x11-gpe net-embedded ... which, IMHO, would be messy.
So, despite "looking" a *lot* of new categories with not so much stuff
inside, will this slow down portage sync/metadata-regen/loopkup in some
way?

Thank you,
-- 
Angelo Arrifano <miknix@gentoo.org>
Gentoo Linux ARM/OMAP850 Developer




  reply	other threads:[~2009-02-03 20:12 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
2009-02-03 20:13     ` Angelo Arrifano [this message]
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=1233691996.22368.25.camel@localhost \
    --to=miknix@gentoo.org \
    --cc=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