| 1 |
* It was Fri, Jul 09, 2004 at 03:00:18PM -0500 when Andrew Gaffney said: |
| 2 |
> Chris Gianelloni wrote: |
| 3 |
> >On Fri, 2004-07-09 at 13:15, John Davis wrote: |
| 4 |
> >When was the last time someone suggest switching from gcc to icc as our |
| 5 |
> >default compiler mid-release? That's right... never. |
| 6 |
> > |
| 7 |
> >You're comparing apples to oranges. I'm not talking about the |
| 8 |
> >stabilization/change of a package *version* but rather of the change in |
| 9 |
> >what many consider an essential function from one package to another. |
| 10 |
> >While it may seem like a small thing to you, when I install from a |
| 11 |
> >2004.1 CD, I know that I'll end up with xfree when I go to install X. |
| 12 |
> >*THIS SHOULD NOT CHANGE* |
| 13 |
> >We are all well aware that the *version* of xfree (or any other package, |
| 14 |
> >for that matter) may change during the time since release, but the |
| 15 |
> >actual packages themselves should be the same. The only exception to |
| 16 |
> >this would be in the case of the original package being completely |
| 17 |
> >removed from the tree. |
| 18 |
> |
| 19 |
> I don't understand why the switch from xfree to xorg-x11 is a big deal. |
| 20 |
> They are currently source and binary compatible. Almost everything (if not |
| 21 |
> everything) works the same with xorg-x11 as it did with xfree. |
| 22 |
|
| 23 |
Yes, thanks to the gentoo devs this is as easy as emerge -C xfree && |
| 24 |
emerge xorg-x11, but I'm sure a lot of work was done to make this |
| 25 |
possible. |
| 26 |
|
| 27 |
-- |
| 28 |
Sami Samhuri |
Archives