public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Is there and Alternative to compiling kde?
Date: Fri, 09 Dec 2005 20:24:01 -0600	[thread overview]
Message-ID: <uwtidy9j2.fsf@newsguy.com> (raw)
In-Reply-To: 20051210002221.211ea496@hactar.digimed.co.uk

Neil Bothwick <neil@digimed.co.uk> writes:

> Those binary packages are supplied by upstream, it's not the same as the
> Gentoo devs providing compiled packages, although they do in the GRP
> collections.
>
> 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.

I'm no stranger to console and `screen' but still hard to beat what
you can do with several desktops, pager  and unlimited xterms.

I'm no where near knowledgable enough to know what I can emerge while
kde is grinding away.... probably should have waited on it, but then
it pulls in some of the other stuff too.

Another big nasty package I have to go is emacs-cvs.  Nasty in this
case because of all the X related stuff if depends on, and of course
I'm in console mode for now so there is a bunch of it for
dependancies.

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?

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-12-10  2:37 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       ` Harry Putnam [this message]
2005-12-10 10:29         ` [gentoo-user] " Neil Bothwick
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=uwtidy9j2.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --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