public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sami Samhuri <sami@no-eff-eks.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x86 2004.2 Profile
Date: Fri, 9 Jul 2004 13:37:58 -0700	[thread overview]
Message-ID: <20040709203758.GK2846@no-eff-eks.com> (raw)
In-Reply-To: <40EEF952.8030405@skylineaero.com>

[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]

* It was Fri, Jul 09, 2004 at 03:00:18PM -0500 when Andrew Gaffney said:
> Chris Gianelloni wrote:
> >On Fri, 2004-07-09 at 13:15, John Davis wrote:
> >When was the last time someone suggest switching from gcc to icc as our
> >default compiler mid-release?  That's right... never.
> >
> >You're comparing apples to oranges.  I'm not talking about the
> >stabilization/change of a package *version* but rather of the change in
> >what many consider an essential function from one package to another. 
> >While it may seem like a small thing to you, when I install from a
> >2004.1 CD, I know that I'll end up with xfree when I go to install X. 
> >*THIS SHOULD NOT CHANGE*
> >We are all well aware that the *version* of xfree (or any other package,
> >for that matter) may change during the time since release, but the
> >actual packages themselves should be the same.  The only exception to
> >this would be in the case of the original package being completely
> >removed from the tree.
> 
> I don't understand why the switch from xfree to xorg-x11 is a big deal. 
> They are currently source and binary compatible. Almost everything (if not 
>  everything) works the same with xorg-x11 as it did with xfree.

Yes, thanks to the gentoo devs this is as easy as emerge -C xfree &&
emerge xorg-x11, but I'm sure a lot of work was done to make this
possible.

-- 
Sami Samhuri

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-09 20:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1089375713.8755.5.camel@antares.hausnetz>
     [not found] ` <1089380082.32612.3.camel@woot.uberdavis.com>
2004-07-09 14:42   ` [gentoo-dev] Re: [gentoo-core] x86 2004.2 Profile Chris Gianelloni
2004-07-09 15:37     ` Grant Goodyear
2004-07-09 16:11       ` [gentoo-dev] " Chris Gianelloni
2004-07-09 17:15         ` John Davis
2004-07-09 18:12           ` Dylan Carlson
2004-07-09 18:28           ` Chris Gianelloni
2004-07-09 20:00             ` Andrew Gaffney
2004-07-09 20:37               ` Sami Samhuri [this message]
2004-07-09 21:07                 ` Donnie Berkholz
2004-07-09 23:16               ` Spider
2004-07-10 18:23                 ` Chris Gianelloni
2004-07-10 19:23                   ` Spider
2004-07-10 19:48                   ` George Shapovalov
2004-07-10 21:36                   ` Dylan Carlson
2004-07-12  1:30                   ` John Davis
2004-08-04 10:52                 ` Paul de Vrieze
2004-07-09 13:51 Benjamin Judas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040709203758.GK2846@no-eff-eks.com \
    --to=sami@no-eff-eks.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox