public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Re: Upgrading from amd64 to ~amd64.
Date: Wed, 19 Oct 2005 08:35:39 -0700	[thread overview]
Message-ID: <pan.2005.10.19.15.35.39.239558@cox.net> (raw)
In-Reply-To: 20051018202551.GA12823@crud.crud.mn.org

Barry.SCHWARTZ posted <20051018202551.GA12823@crud.crud.mn.org>, excerpted
below,  on Tue, 18 Oct 2005 15:25:51 -0500:

> These days I run ~amd64 by default, but with the glibc from amd64. I
> found cups and the whole apache-php-subversion thing difficult to
> manage as ~amd64 so I also use the amd64 version there.

Interesting...  Here, I'm running a still-masked gcc-4.0.1, with
dependencies on a binutils that was at least still masked when I unmasked
and merged it.  Additionally, as part of the gcc4 thing, I'm running a
still-masked glibc snapshot that has gcc4 fixes.

So... one could say I'm at the opposite extreme as you... you stay stable
amd64 for glibc and etc, I use package.unmask to get stuff that's not even
in ~amd64 yet!  =8^)

Of course, part of that probably has to do with something else you
mention, that whole apache-php-subversion thing.  That implies the purpose
of your installation is server related, and servers traditionally run more
conservative settings, DEFINITELY so if they are publicly accessible or
mission critical.  

I'm lucky enough to have a dual Opteron as my private desktop workstation,
where computing is my hobby, not my job, so if it breaks and takes a
couple days for me to figure out what's wrong and get things up and
running again, no big deal, that's simply part of the challenge that makes
my hobby enjoyable enough to keep me coming back for more!  =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-10-19 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  2:50 [gentoo-amd64] Upgrading from amd64 to ~amd64 Toby Fisher
2005-10-18  3:09 ` Barry.SCHWARTZ
2005-10-18  3:15 ` Mark Knecht
2005-10-18  3:55 ` Richard Freeman
2005-10-18 11:09   ` [gentoo-amd64] " Duncan
2005-10-18 15:58     ` Scott Stoddard
2005-10-19 15:25       ` [gentoo-amd64] " Duncan
2005-10-18 20:25     ` [gentoo-amd64] " Barry.SCHWARTZ
2005-10-19 15:35       ` Duncan [this message]
2005-10-19 16:06         ` [gentoo-amd64] " Barry.SCHWARTZ
2005-10-18 20:29     ` [gentoo-amd64] " Barry.SCHWARTZ
2005-10-18 15:28 ` [gentoo-amd64] " Peter Humphrey

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=pan.2005.10.19.15.35.39.239558@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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