1 |
On Monday 10 June 2002 16:15, Pieter Van den Abeele wrote: |
2 |
|
3 |
> The cracklib ebuild I fixed a while ago, was a very good example of how |
4 |
> bad some ebuilds are written. It almost seemed to me that nobody actually |
5 |
> knew what the stuff did. |
6 |
> |
7 |
|
8 |
Yep, I have seen many cases of this throughout some builds. Other builds are |
9 |
excellent, and many are between. |
10 |
|
11 |
> As long as the x86 devs don't start removing ppc stuff, I'm happy :-) |
12 |
|
13 |
only happened once AFAIK ;) |
14 |
|
15 |
> |
16 |
> Can you please explain this problem to me in a few lines, I cannot imagine |
17 |
> it being such a big problem. |
18 |
|
19 |
It's a long explanation (i posted a bit of it to -core) and I think I have a |
20 |
workaround for it now (albeit not very elegant but it should work). |
21 |
|
22 |
> My motto is: try to avoid breaking things and tell maintainers. |
23 |
> If they prefer to rewrite your fix, make them email you and ask them to |
24 |
> test it :-) |
25 |
> |
26 |
|
27 |
Yep, I've followed protocol to date ;) |
28 |
|
29 |
> We had a long discussion about this on gentoo-alt, and at the time it |
30 |
> seemed that the ARCH stuff would be |
31 |
> |
32 |
|
33 |
It may yet still be great, IMHO its just more difficult to manage the |
34 |
possibility of arch's being split across files, etc than it is to manage |
35 |
duplicate (or near duplicate) files...but the more i think of the |
36 |
possibilities the more I like daniels solution with group masking as well |
37 |
(tweaked). |
38 |
|
39 |
> |
40 |
> It is possible to use separate ARCH files using eclasses. Check gentoo-alt |
41 |
> logs. But in some cases separate files would be better. I even suggested a |
42 |
> portage painting system so that x86 platforms only download x86 ebuilds |
43 |
> etc. (This can in fact easily be combined with the GROUPS stuff) |
44 |
|
45 |
I think even something as simple as the ability to have say foo-1.0.ebuild and |
46 |
(if neccesary to override anything drastic like a whole seperate build) |
47 |
foo-1.0-ppc.ebuild. This could also allow the ability to name |
48 |
foo-10.-ppc.ebuild as a ppc only ebuild (or vica versa for another arch). |
49 |
This may become more relevant when a 3rd arch is introduced as well. |
50 |
|
51 |
|
52 |
> Masking everything seems a bit drastic to me. |
53 |
> |
54 |
|
55 |
Yes, maybe you are right. But I think that we shold at least try to compile a |
56 |
list on known 'working' builds and masking out everything else. I imagine |
57 |
there are a great many builds that just aren't going to work on ppc right |
58 |
now. Then as builds are known working we could add them (and unmask). Or |
59 |
even possibly just maintain a list of known workin builds on the website |
60 |
somewhere...some kind of clue. It was kind of comical trying to explain why |
61 |
vmware wouldn't work on someone's ppc, they just weren't taking no for an |
62 |
answer (more obvious ones are now currently masked). |
63 |
|
64 |
> Yes, I also think Ebuild categories should be appointed to certain |
65 |
> maintainers responsible for that category. They should be supervising the |
66 |
> changes made to their section. |
67 |
> |
68 |
|
69 |
Yes, that would be very very good I think too. |
70 |
|
71 |
> I don't know if I've already suggested this; but it might be a good idea |
72 |
> to have a daily/weekly/monthly snapshot mirror. People could try to get |
73 |
> things fixed by snapshot time. |
74 |
> |
75 |
|
76 |
I think that would be nice too, and it would prevent most accidental or |
77 |
improperly masked builds to get into the wild. |
78 |
|
79 |
|
80 |
> I have a nasty timezone problem (I'm asleep when everybody is awake, so |
81 |
> IRC is not very usefull to me) I do try to be on IRC when I'm not working |
82 |
> and I can afford to spend whole nights on irc. Just send me an email if |
83 |
> you like me to attend a irc meeting, I won't be on IRC this month because |
84 |
> of a system crash (my gentoo dev box is toast) and I'm having exams. :-( |
85 |
> |
86 |
|
87 |
Hmmm, yes i can see this being a bit difficult, I believe Doc shares your time |
88 |
zone as well. I don't know a better soltuion aside from email tag though. |
89 |
Anyone have any ideas? |
90 |
|
91 |
Mark |