| 1 |
On Ter, 2009-02-03 at 11:47 -0800, Donnie Berkholz wrote: |
| 2 |
> On 11:24 Tue 03 Feb , Donnie Berkholz wrote: |
| 3 |
> > > We currently provide an eclass and ebuilds arranged by top level |
| 4 |
> > > categories following upstream categorization. Explicitly gpe.eclass and |
| 5 |
> > > top level gpe-base gpe-net gpe-pim gpe-games gpe-utils gpe-media |
| 6 |
> > > gpe-xsession. |
| 7 |
> > > We know we have a lot of them but upstream finds useful to classify them |
| 8 |
> > > like that and so do we. |
| 9 |
> > |
| 10 |
> > Could you expand on how each new category is useful? |
| 11 |
|
| 12 |
In my maintainer point of view, it just make sense to follow upstream |
| 13 |
categorization of packages. |
| 14 |
|
| 15 |
In the user centric view, it will be a lot more easier to know what |
| 16 |
package is for by looking at each category. |
| 17 |
gpe-xxxx is intended for embedded devices, one might want to keep it |
| 18 |
clean and minimal. |
| 19 |
|
| 20 |
> > |
| 21 |
> > > The eclass and some ebuilds were based on bugzie #101393. We started |
| 22 |
> > > playing with them as big flat gpe-base category which evolved over time |
| 23 |
> > > by means of consecutive testing on ARMv5 handheld devices and needs. |
| 24 |
> > > |
| 25 |
> > > Since we are maintaining this over half a year now, we think that its |
| 26 |
> > > time to finally starting moving step-by-step the GPE suite into the |
| 27 |
> > > portage tree - starting with the eclass and toplevel categories. |
| 28 |
> > |
| 29 |
> > What are the stats on package count per category? |
| 30 |
> |
| 31 |
> I got this from solar: |
| 32 |
> |
| 33 |
> 30 gpe-base |
| 34 |
> 8 gpe-games |
| 35 |
> 4 gpe-media |
| 36 |
> 9 gpe-misc |
| 37 |
> 2 gpe-net |
| 38 |
> 32 gpe-phone |
| 39 |
> 6 gpe-pim |
| 40 |
> 18 gpe-utils |
| 41 |
> 8 gpe-xsession |
| 42 |
> |
| 43 |
> Unless those tiny ones are going to be growing a lot, I'm not terribly |
| 44 |
> convinced of this many new ones. |
| 45 |
> |
| 46 |
|
| 47 |
They won't grow much over time so I understand your point. |
| 48 |
Although, I would like to ask the drawbacks of adding those new |
| 49 |
categories to portage. |
| 50 |
Adding confusion and mess won't be an issue because these are very |
| 51 |
specific categories which won't affect other ebuilds or other |
| 52 |
categories. |
| 53 |
After all we don't want to introduce something like dev-gpe mail-gpe |
| 54 |
x11-gpe net-embedded ... which, IMHO, would be messy. |
| 55 |
So, despite "looking" a *lot* of new categories with not so much stuff |
| 56 |
inside, will this slow down portage sync/metadata-regen/loopkup in some |
| 57 |
way? |
| 58 |
|
| 59 |
Thank you, |
| 60 |
-- |
| 61 |
Angelo Arrifano <miknix@g.o> |
| 62 |
Gentoo Linux ARM/OMAP850 Developer |
Archives