1 |
On Sun, 2001-11-11 at 14:08, Claes Nästen wrote: |
2 |
> * Martin Schlemmer (azarah@g.o) wrote: |
3 |
> > Hi |
4 |
> > |
5 |
> > Something we really need at the moment is a pcmcia-cs ebuild, |
6 |
> > but due to reasons i cannot remember, you cant have just a |
7 |
> > default ebuild, but should need to provide source as well |
8 |
> > if needed. |
9 |
> > |
10 |
> > Danarmak and me talked about this some while back, but neither |
11 |
> > of us got to it as of yet. |
12 |
> > |
13 |
> > A nice option whould be to split ebuild of this kind into 3: |
14 |
> > |
15 |
> > modules |
16 |
> > source |
17 |
> > userland-tools |
18 |
> > (maybe libs as well .. like lm_sensors ??) |
19 |
> > |
20 |
> > Only problem i for see with this, is that there is no real |
21 |
> > place for ebuild of this kind. |
22 |
> > |
23 |
> > Also other drivers (nvidia, any other addon (the glide modules?) have no |
24 |
> > real place in the portage tree. |
25 |
> > |
26 |
> > Now, what I suggests is that we move things around a bit, and |
27 |
> > create some new portage catagories: |
28 |
> > |
29 |
> > kernel-headers |
30 |
> > linux-headers |
31 |
> > pcmcia-cs-headers |
32 |
> > lm_sensors-headers (if needed) |
33 |
> > alsa-headers |
34 |
> > |
35 |
> |
36 |
> Wouldn't kernel-header be kinda confusing as it sounds as if it _belongs_ to th e kernel tree. Why not make an drivers category like: |
37 |
> |
38 |
> drivers(? maybe a better name) |
39 |
> lm_sensors |
40 |
> lm_sensors-tools |
41 |
> lm_sensors-headers |
42 |
> |
43 |
> and so on, seems more logical to me. |
44 |
> |
45 |
|
46 |
Because the kernel is not a driver, and since everything in |
47 |
here is kernel related, it seems to me like the best choise. |
48 |
|
49 |
> > kernel-modules (also any binaries .. like the kernel) |
50 |
> > linux |
51 |
> > pcmcia-cs-modules |
52 |
> > lm_sensors-modules |
53 |
> > i2c-modules |
54 |
> > nvidia-modules |
55 |
> > alsa-modules |
56 |
> > ... |
57 |
> > |
58 |
> > kernel-source |
59 |
> > linux-sources |
60 |
> > linux-sources-vanilla |
61 |
> > pcmcia-cs-sources |
62 |
> > lm_sensors-sources |
63 |
> > i2c-sources |
64 |
> > alsa-sources |
65 |
> > |
66 |
> > kernel-tools |
67 |
> > ksymoops |
68 |
> > pcmcia-cs-tools |
69 |
> > lm_sensors-tools |
70 |
> > alsa-utils/tools |
71 |
> > |
72 |
> > kernel-libs (??) |
73 |
> > lm_sensors-libs |
74 |
> > alsa-libs |
75 |
> > |
76 |
> > And so on. |
77 |
> > |
78 |
> > Another plus of doing it this way (except the lots of work |
79 |
> > ;p), is that things will be easier to find for new users. |
80 |
> > |
81 |
> > The kernel-source stuff can tipically install into |
82 |
> > /usr/src/kernel-extra or some other default location |
83 |
> > |
84 |
> > I have already commited myself to doing i2c and lm_sensors, |
85 |
> > danarmak said he will do pcmcia-cs, and the rest should not |
86 |
> > be a biggy. |
87 |
> > |
88 |
> > Anyway, this is still a very _alph_ idea ;) So let me know |
89 |
> > what you think! |
90 |
> > |
91 |
> > |
92 |
> > Greetings, |
93 |
> > -- |
94 |
> > |
95 |
> > Martin Schlemmer |
96 |
> > Gentoo Linux Developer, Desktop Team Developer |
97 |
> > Cape Town, South Africa |
98 |
> > |
99 |
> |
100 |
> |
101 |
> |
102 |
> _______________________________________________ |
103 |
> gentoo-dev mailing list |
104 |
> gentoo-dev@××××××××××.org |
105 |
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev |
106 |
-- |
107 |
|
108 |
Martin Schlemmer |
109 |
Gentoo Linux Developer, Desktop Team Developer |
110 |
Cape Town, South Africa |