1 |
Grant Goodyear posted <20050831161516.GJ18440@×××××××××××××.edu>, |
2 |
excerpted below, on Wed, 31 Aug 2005 11:15:16 -0500: |
3 |
|
4 |
> Stephen P. Becker wrote: [Wed Aug 31 2005, 08:18:53AM CDT] |
5 |
>> We don't "live with that problem on MIPS" because it doesn't exist. If |
6 |
>> something doesn't work in one spot, we dont' stable keyword it...simple |
7 |
>> as that. Also keep in mind that for some stuff, we don't have to test |
8 |
>> on both. For example, we have no supported little endian machines that |
9 |
>> are capable of running X, therefore, we don't care about testing X |
10 |
>> there. See how it works? |
11 |
> |
12 |
> So, the basic suggestion is that x86 and amd64 would both use the same |
13 |
> keyword, but that for cases such as valgrind pre-3.0, which didn't work |
14 |
> at all on amd64, then those package are profile-masked, and there's |
15 |
> separate amd64 and x86 profiles (as there are now) to handle those |
16 |
> distinctions? |
17 |
|
18 |
Thanks!... Now that's something concrete enough to wrap my brain around, |
19 |
which is exactly what I was asking for. Consider the "magic" explained. |
20 |
Like so much "magic", there's a perfectly good explanation, once you grasp |
21 |
the concept! =8^) |
22 |
|
23 |
I still don't necessarily think it's the best solution for a problem that |
24 |
seems decently solved as it is (not that my opinion really counts anyway, |
25 |
as just a user, not one of the many actually doing the work), but at |
26 |
least I have a clue about how it can be done, now, something I was lacking |
27 |
the "Eureka moment" necessary to grasp, previously. =8^) Now I can at |
28 |
least intelligently follow the debate. |
29 |
|
30 |
-- |
31 |
Duncan - List replies preferred. No HTML msgs. |
32 |
"Every nonfree program has a lord, a master -- |
33 |
and if you use the program, he is your master." Richard Stallman in |
34 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
35 |
|
36 |
|
37 |
-- |
38 |
gentoo-dev@g.o mailing list |