1 |
Uhm, what is this all about? If you have suggestions, make them, but |
2 |
don't come out of the gate in a huff talking about unsubstantiated |
3 |
breakage. That's about the least constructive way to get heard. |
4 |
|
5 |
The wrapper provided in gcc-config-2.0 provides the exact same |
6 |
interface to the user as gcc-config-1.x, so how is that breaking |
7 |
expected behavior? If anything, it's providing expected behavior to |
8 |
users who want it and don't care about migrating over to eselect. |
9 |
Additionally, If you check through the ChangeLog, you'll see that I |
10 |
did actively worked on gcc-config-1.x last year prior to my starting |
11 |
eselect-compiler. That's how I came to realize its limitations and |
12 |
_need_ for replacement on multilib systems. A similar wrapper is |
13 |
needed for binutils as has been discussed multiple times on |
14 |
toolchain@, and at amd64 and ppc64 dev meetings on IRC. |
15 |
|
16 |
Additionally, eselect-compiler has been discussed multiple times on |
17 |
the toolchain and gentoo-dev lists over the past year (main threads |
18 |
started 2005-08-09, 2005-09-17, 2005.10.02), and you didn't once |
19 |
raise an objection until now. I'd say you missed the 10 month window |
20 |
I gave you, but if you do have suggestions, I'd be more than happy to |
21 |
hear them. |
22 |
|
23 |
Even more so, I left eselect-compiler in package.mask for a _very_ |
24 |
long time as I didn't have much time to devote to its development |
25 |
over the past school year. During that time, very few issues were |
26 |
raised despite it being used by many testers and developers. This |
27 |
past month, I worked out all but one of the known bugs (the one |
28 |
remaining is just specific to the wine package on amd64) and got more |
29 |
testers to give it a final beating before finally unmasking it. If |
30 |
anything, this has been an extremely conservative development process |
31 |
because of the nature of this package. |
32 |
|
33 |
--Jeremy |
34 |
|
35 |
On Jun 6, 2006, at 04:28 , Ned Ludd wrote: |
36 |
|
37 |
> Why are you hijacking tools not written by you, declaring |
38 |
> them as 2.0 and breaking the expected behaviors of them? |
39 |
> |
40 |
> Please don't do that ever again. |
41 |
> |
42 |
> |
43 |
> On Fri, 2006-06-02 at 21:24 -0700, Jeremy Huddleston wrote: |
44 |
>> I finally had a few free cycles, so I fixed up the eselect-compiler |
45 |
>> ebuild to better handle the transition from gcc-config and updated |
46 |
>> toolchain.eclass to better work with multilib. I've had a bunch of |
47 |
>> help from the amd64 devs/testers/users this past week testing it out, |
48 |
>> and I think it's ready to be removed from package.mask sometime soon |
49 |
>> (next week). Before that happens, I'd like to get some feedback from |
50 |
>> a broader test base, so if you have some time and aren't using |
51 |
>> eselect-compiler yet, I'd appreciate your testing. All you need to |
52 |
>> do is add the following to /etc/portage/package.unmask: |
53 |
>> |
54 |
>> app-admin/eselect-conmpiler |
55 |
>> sys-devel/gcc-config |
56 |
>> |
57 |
>> then just update gcc-config: |
58 |
>> $ emerge -uv --oneshot sys-devel/gcc-config |
59 |
>> |
60 |
>> gcc-config is just a wrapper which takes the same syntax as the older |
61 |
>> gcc-configs and makes the appropriate call to eselect-compiler. |
62 |
>> |
63 |
>> Please report any bugs you find in bugzilla and assign them directly |
64 |
>> to me (eradicator@g.o). |
65 |
>> |
66 |
>> Also, if you've been using eselect-compiler, you may have an issue |
67 |
>> where your profiles don't get removed from /etc/eselect/compiler when |
68 |
>> you unmerge gcc. This problem is fixed now for future installs, but |
69 |
>> you'll have to manually remove the file when you unmerge any gcc that |
70 |
>> is on your system now. |
71 |
>> |
72 |
>> Thanks, |
73 |
>> Jeremy |
74 |
>> |
75 |
> -- |
76 |
> Ned Ludd <solar@g.o> |
77 |
> Gentoo Linux |
78 |
> |
79 |
> -- |
80 |
> gentoo-dev@g.o mailing list |
81 |
> |
82 |
|
83 |
-- |
84 |
gentoo-dev@g.o mailing list |