public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gerhard Hoogterp <gerhard@frappe.xs4all.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Is there and Alternative to compiling kde?
Date: Sat, 10 Dec 2005 15:59:25 +0100	[thread overview]
Message-ID: <200512101559.25873@frappe.xs4all.nl> (raw)
In-Reply-To: <439AB4CB.6070508@planet.nl>

On Saturday 10 December 2005 11:58, Holly Bostick wrote:
> Gerhard Hoogterp schreef:

> > While this is true and one of the things that makes gentoo gentoo,
> > there are already binary packages in portage. mozilla-bin,
> > openoffice-bin. Mostly big packages which take some time to compile.
> >  So the idea of having a pre-compiled KDE isn't that alien to the
> > world of gentoo..
>
> Oh, phooey,  Gerhard (sorry).

NP.. happily phooey away..;-) It wasn't my question and I already did my 
compile session.. Only 3 days due to some hurdles, toxml who dosn't know 
about its dependency on libxlst and hal wanting a newer kernel (but not MM- 
as it doesn't seem to have the needed feature.. so back to gentoo kernel.. ) 
But oh well, that's the goodness that's gentoo and sorting it out yourself 
gives on that soft glowing "almost-guru" feeling..;-)

> People, it's not like KDE just got huge yesterday or something.

Nope, but on a slow machine it IS big.. and trying to keep an 400mhz amd-k6 
somewhat up to date as a gateway (without KDE, but compiling glibc or 
apache/php/mysql isn't much fun either) I can see that's a problem for some. 
Of course the question is if they should run kde on such a machine, but 
that's up to them..  I don't blame them for asking. But seeing my hurdles 
while upgrading, I doubt that just binary kde packages is going to help them 
much. 

Gerhard
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-12-10 15:06 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
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 [this message]
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=200512101559.25873@frappe.xs4all.nl \
    --to=gerhard@frappe.xs4all.nl \
    --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