public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Segregating KDE?
Date: Sat, 18 Sep 2004 12:16:08 +0300	[thread overview]
Message-ID: <200409181216.16581.danarmak@gentoo.org> (raw)
In-Reply-To: <200409180057.34014.anthony@ectrolinux.com>

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

On Saturday 18 September 2004 10:57, Anthony Gorecki wrote:
> If Gentoo is committed to offering users a large degree of customizability,
> wouldn't segregating the various KDE components lend itself to continuing
> the evolution of that flexibility? I would cheer at the ability to type
> "emerge kmail" rather than "emerge kdepim".

This defnitely should go onto our FAQ if we have one.

Please see bug #11123 for the previous discussion on the subject.

This is the key paragraph quoted from there:
A kde configure script takes as much as a minute or more to run. Today when 
you emerge all of kde you run ~17 configure scripts, i.e. as much as 20 
minutes goes there (of course everything depends on the speed of the 
machine). If all kde-base packages are split into separate subpackage 
ebuilds, you'll get hundreds of subpackags (200+). That means an extra 200 
minutes -- 3.5 hours -- added to the compilation time of all of KDE. And most 
people do want the whole of kde. This is unacceptable

That said, the recent config-cache patch to portage, if accepted, could make 
this rather painless, so now this issue is finally worth raising again. (And 
perhaps unsermake could also help somehow?) I haven't tried it out yet 
though, so let's have some active KDE maintainer comment ;-)

-- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951

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

  reply	other threads:[~2004-09-18  9:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18  7:57 [gentoo-dev] Segregating KDE? Anthony Gorecki
2004-09-18  9:16 ` Dan Armak [this message]
2004-09-18 18:02   ` Anthony Gorecki
2004-09-18 18:29     ` Dan Armak
2004-09-18 18:31       ` Dan Armak
2004-09-18 19:19         ` Seemant Kulleen
2004-09-18 19:36           ` Dan Armak
2004-09-19  8:30             ` Simone Gotti
2004-09-19 14:48               ` Dan Armak
2004-09-19 18:08                 ` Simone Gotti
2004-09-19 19:33                   ` Dan Armak
2004-09-19 19:42                     ` Dan Armak
2004-09-19 19:59                       ` Dan Armak
2004-09-19 21:00                     ` Simone Gotti
2004-09-21  0:10                     ` Simone Gotti
2004-09-18 19:09       ` Anthony Gorecki
2004-09-18 19:45         ` Dan Armak
2004-09-18 20:13           ` Anthony Gorecki
2004-09-18 20:33             ` Sami Samhuri
2004-09-18 20:33               ` Anthony Gorecki
2004-09-18 20:38             ` Dan Armak
2004-09-18 20:40               ` Dan Armak
2004-09-19  4:43     ` [gentoo-dev] " Duncan
2004-09-19 14:56       ` Dan Armak
2004-09-19 19:46         ` Paul de Vrieze
2004-09-18 13:11 ` [gentoo-dev] " Caleb Tennis
2004-09-18 14:06   ` Nick Dimiduk

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=200409181216.16581.danarmak@gentoo.org \
    --to=danarmak@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