public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Is there and Alternative to compiling kde?
Date: Sat, 10 Dec 2005 10:29:09 +0000	[thread overview]
Message-ID: <20051210102909.5edd8bc1@hactar.digimed.co.uk> (raw)
In-Reply-To: <uwtidy9j2.fsf@newsguy.com>

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

On Fri, 09 Dec 2005 20:24:01 -0600, Harry Putnam wrote:


> > It's no big deal upgrading KDE anyway. Set PORTAGE_NICENESS to a
> > suitable value and you can keep using the computer while the new KDE
> > is compiled in the background. KDE is slotted, so installing 3.5 has
> > no effect on the 3.4.x version you are currently using.
> 
> Good tips, thanks... but in this case I'm running a full install from
> scratch and would like to be emerging some of the other needed stuff.
> That task would be somewhat lessened too just by having X available.

Then download a GRP CD, do a stage 3 install then install, X, KDE etc.
from the GRP CD. That's how I did it and had a full working system in
just over and hour. I was able to set my USE flags, sysnc portage and
re-emerge everything that needed  it later on.

> Do you know off-hand if I would be digging myself into a hole by
> running and emerge emacs-cvs while this pentium4 is gnawing away at
> kde?

Generally, as long as the packages have nothing to do with one another,
it is safe to install concurrently. To be really safe, you could use
Ctrl-z to pause one emerge while installing another package, then type
"fg" to restart". I'd go for the GRP packages though, and upgrade later
in the background.


-- 
Neil Bothwick

Run with scissors. Remove mattress tags. Top post. Be a rebel.

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

  reply	other threads:[~2005-12-10 10:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 21:55 [gentoo-user] Is there and Alternative to compiling kde? Harry Putnam
2005-12-09 22:08 ` Jeff
2005-12-09 22:20 ` Tom Smith
2005-12-09 22:35   ` Gerhard Hoogterp
2005-12-09 22:50     ` Dale
2005-12-09 22:58     ` Tom Smith
2005-12-10  0:22     ` Neil Bothwick
2005-12-10  2:24       ` [gentoo-user] " Harry Putnam
2005-12-10 10:29         ` Neil Bothwick [this message]
2005-12-10 13:52           ` Harry Putnam
2005-12-10  1:39     ` Harry Putnam
2005-12-10 10:58     ` [gentoo-user] " Holly Bostick
2005-12-10 14:59       ` Gerhard Hoogterp
2005-12-10 15:44       ` Neil Bothwick
2005-12-09 23:02 ` Chris White
2005-12-10  0:42   ` Dale
2005-12-10  1:46     ` [gentoo-user] " Daniel da Veiga
2005-12-10  1:59       ` Harry Putnam
2005-12-14  3:07       ` Daevid Vincent
2005-12-14  6:14         ` Steven Susbauer
2005-12-14  6:20         ` Richard Fish
2005-12-14 20:42           ` Christoph Eckert
2005-12-14  9:43         ` Holly Bostick
2005-12-14 10:40         ` Neil Bothwick
2005-12-10  1:37   ` Harry Putnam
2005-12-10  1:47   ` Harry Putnam
2005-12-10  8:17     ` Chris White
2005-12-10 13:49       ` Harry Putnam
2005-12-10 15:49         ` Neil Bothwick
2005-12-10 16:31           ` Harry Putnam
2005-12-10 16:49             ` Brett I. Holcomb
2005-12-10 17:09             ` Neil Bothwick
2005-12-10 17:56 ` [gentoo-user] " Spider (D.m.D. Lj.)

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=20051210102909.5edd8bc1@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@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