1 |
Hmm... |
2 |
|
3 |
I like it. |
4 |
|
5 |
If we do that; we could put a nice script to list all the packages from one |
6 |
category, |
7 |
so perhaps something like : |
8 |
|
9 |
DESCRIPTION="A graphical file comparator and merge tool simular to xdiff." |
10 |
EMERGE_CATEGORY="dev-util" |
11 |
EMERGE_CATEGORY="x11-misc" |
12 |
SRC_URI="http://prdownloads.sourceforge.net/xxdiff/${P}.src.tar.gz" |
13 |
|
14 |
|
15 |
would be better (simple grep would then do what we want)... |
16 |
|
17 |
/Maciek |
18 |
|
19 |
|
20 |
Sean Mitchell wrote: |
21 |
|
22 |
> This is probably the single biggest issue on this list. It seems that every |
23 |
> day there's a post questioning why an ebuild is in a given location and not |
24 |
> some other. |
25 |
> |
26 |
> I really don't see how anyone could ever come up with a structure that's |
27 |
> intuitive for everyone... we just don't all think the same way. For myself, |
28 |
> I don't even bother with the structure, I prefer to do a find on *.ebuild in |
29 |
> /usr/portage to see what's there. |
30 |
> |
31 |
> A few years ago I put together a series of OS/2 shareware CDs and had the |
32 |
> same problem - many packages didn't clearly fit in one place or another. |
33 |
> |
34 |
> The solution I came up with and the one I suggest here is that the |
35 |
> categories be eliminated altogether. in this case one big /usr/portage with |
36 |
> a directory for each package. |
37 |
> |
38 |
> I mean, it's easy enough to grep the description fields, or even put all |
39 |
> possible categories in a new tag in the ebuild. It would be simple to put |
40 |
> together some tools to show the packages by category if desired. |
41 |
> |
42 |
> Something like: |
43 |
> |
44 |
> S=${WORKDIR}/${P} |
45 |
> DESCRIPTION="A graphical file comparator and merge tool simular to xdiff." |
46 |
> CATEGORY="dev-util x11-misc" |
47 |
> SRC_URI="http://prdownloads.sourceforge.net/xxdiff/${P}.src.tar.gz" |
48 |
> HOMEPAGE="http://xxdiff.sourceforge.net/" |
49 |
> |
50 |
> What do you think? |
51 |
> |
52 |
> Sean |
53 |
> _______________________________________________ |
54 |
> gentoo-dev mailing list |
55 |
> gentoo-dev@g.o |
56 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |