1 |
>> but how about make more than 2 |
2 |
>> levels in portage, as in OpenBSD's ports tree ? |
3 |
|
4 |
My personal feeling is that many packages don't belong in only one |
5 |
category. E.g. in portage currently: |
6 |
|
7 |
* app-text/yudit |
8 |
Description: free (Y)unicode text editor for all unices |
9 |
|
10 |
* app-editors/jedit |
11 |
Description: Programmer's editor written in Java |
12 |
|
13 |
Both make sense, and app-editors/yudit & app-editors/yudit would |
14 |
also make sense. Instead of categories, ebuilds should have a |
15 |
CATEGORY variable. E.g. |
16 |
|
17 |
""" |
18 |
DESCRIPTION="free (Y)unicode text editor for all unices" |
19 |
SRC_URI="http://yudit.org/download/${P}.tar.gz" |
20 |
HOMEPAGE="http://www.yudit.org/" |
21 |
CATEGORY="app-text app-editors" # <= all categories that make sense |
22 |
""" |
23 |
|
24 |
App directories can then be in one directory, or can be split by |
25 |
letter to keep the number of files per directory smaller (e.g. |
26 |
|
27 |
/usr/portage/aa/aa-sources |
28 |
/usr/portage/aa/aalib |
29 |
/usr/portage/aa/aap |
30 |
/usr/portage/aa/aaquake2 |
31 |
/usr/portage/ab/abcde |
32 |
/usr/portage/ab/abcm2ps |
33 |
/usr/portage/ab/abiword |
34 |
/usr/portage/ab/abook |
35 |
|
36 |
Then you do `emerge search app-text` instead of |
37 |
`ls /usr/portage/app-text`, and guessing whether vim is there, |
38 |
or in app-vim or in app-editors. |
39 |
|
40 |
-- |
41 |
Jean Jordaan |
42 |
http://www.upfrontsystems.co.za |
43 |
|
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |