1 |
Adam Piątyszek wrote: |
2 |
> * Donnie Berkholz [2006-05-29 10:26]: |
3 |
> > This problem should only happen when you first use the eselect version, |
4 |
>> then switch back to the *-config version, then switch to the eselect |
5 |
>> version again. I don't consider it a real bug, because of this. |
6 |
>> |
7 |
>> The deal is that /etc/env.d/lapack/config will specify the |
8 |
>> CURRENT="$foo" setting, but it can't know about how things are set up |
9 |
>> using *-config rather than the eselect modules. |
10 |
> |
11 |
> So, it seems that the new eselect tool is not backward compatible with |
12 |
> previous approaches, which is in my opinion not a good idea. A user might |
13 |
> have mixed x86 and ~x86 packages installed and therefore some of them uses |
14 |
> old *-config scripts and others your new eselect tool. In such a situation |
15 |
> there is no convenient method to switch between libraries... |
16 |
> |
17 |
> That is of course my point of view, from the user's perspective. |
18 |
|
19 |
In my opinion, adding extra code to deal with an old approach is a bad |
20 |
idea and will quickly introduce cruft into a new replacement. |
21 |
|
22 |
Supporting mixed testing-stable systems is not a goal. Supporting |
23 |
all-~x86 and all-x86 systems is a goal. |
24 |
|
25 |
Thanks, |
26 |
Donnie |