1 |
This is probably the single biggest issue on this list. It seems that every |
2 |
day there's a post questioning why an ebuild is in a given location and not |
3 |
some other. |
4 |
|
5 |
I really don't see how anyone could ever come up with a structure that's |
6 |
intuitive for everyone... we just don't all think the same way. For myself, |
7 |
I don't even bother with the structure, I prefer to do a find on *.ebuild in |
8 |
/usr/portage to see what's there. |
9 |
|
10 |
A few years ago I put together a series of OS/2 shareware CDs and had the |
11 |
same problem - many packages didn't clearly fit in one place or another. |
12 |
|
13 |
The solution I came up with and the one I suggest here is that the |
14 |
categories be eliminated altogether. in this case one big /usr/portage with |
15 |
a directory for each package. |
16 |
|
17 |
I mean, it's easy enough to grep the description fields, or even put all |
18 |
possible categories in a new tag in the ebuild. It would be simple to put |
19 |
together some tools to show the packages by category if desired. |
20 |
|
21 |
Something like: |
22 |
|
23 |
S=${WORKDIR}/${P} |
24 |
DESCRIPTION="A graphical file comparator and merge tool simular to xdiff." |
25 |
CATEGORY="dev-util x11-misc" |
26 |
SRC_URI="http://prdownloads.sourceforge.net/xxdiff/${P}.src.tar.gz" |
27 |
HOMEPAGE="http://xxdiff.sourceforge.net/" |
28 |
|
29 |
|
30 |
What do you think? |
31 |
|
32 |
Sean |