public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x86 2004.2 Profile
Date: Fri, 09 Jul 2004 12:11:40 -0400	[thread overview]
Message-ID: <1089389500.11041.64.camel@localhost> (raw)
In-Reply-To: <20040709153740.GA7982@orange-pc.ces.clemson.edu>

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

On Fri, 2004-07-09 at 11:37, Grant Goodyear wrote:
> Chris Gianelloni wrote: [Fri Jul 09 2004, 10:42:59AM EDT]
> > For consitency's sake, yes, it is necessary.  I don't want to build a
> > machine today using the 2004.0 profile and build a machine tomorrow
> > using *the same profile* and have one using xfree and one using
> > xorg-x11.
> 
> Just to make sure I understand, you're suggesting a new profile that
> removes the absolutely pointless xfree line in the packages file
> (pointless because it's not a system file and we haven't had any xfree
> ebuilds in portage that fail to satisfy the requirement since probably
> the 1.2 days) and change the default x11 virtual to point to xorg-x11?

Yes, the removal of the xfree line from packages would be done.  I would
also change the default virtual for x11, opengl, glu, and xft.

> It's not really clear to me that a new profile needs to be created every
> time a default virtual changes.  My reasoning is that any user who
> already has something installed that satisfies that virtual will see
> absolutely no difference with the new profile.  With X, that would be the
> vast majority of our users, who then might well be more confused
> that using the new profile does _not_ cause them to upgrade to xorg-x11.

I understand that users that switch profiles will see no difference, and
am fine with that.  I'm not worried about people that do that, since we
will in essence not be affecting them at all.  Since the switch from
xfree to xorg-x11 has the potential to be so wide-spread, I think it
should be done with the creation of a new profile.

The idea of changing a virtual mid-release has *always* bothered me and
is a prime example of Gentoo's problems when it comes to enterprise
users.  In an enterprise environment, consistency between releases is
expected.  I should *never* have to wonder which X server got installed
between on each machine between multiple 2004.2 installations.  I should
*know* that 2004.0 and 2004.1 used XFree86 and that 2004.2+ uses X.org's
server.

I have no problem dealing with the users that switch their profiles
themselves and then wonder why they didn't switch X servers rather than
dealing with the inconsistency between installs.

If GCC 3.4 were ready for wide-spread usage, I would recommend changing
it in the packages file, also.  Unfortunately, it is not at that point
yet, so we are not making such a change.

-- 
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux

Is your power animal a penguin?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-09 16:09 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       ` Chris Gianelloni [this message]
2004-07-09 17:15         ` [gentoo-dev] " 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
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=1089389500.11041.64.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --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