public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Anthony Gorecki <anthony@ectrolinux.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Segregating KDE?
Date: Sat, 18 Sep 2004 11:02:53 -0700	[thread overview]
Message-ID: <200409181103.01872.anthony@ectrolinux.com> (raw)
In-Reply-To: <200409181216.16581.danarmak@gentoo.org>

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

On Saturday 18 September 2004 2:16 am, Dan Armak wrote:
> 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+). 

Perhaps instead of using completely independent packages for the software 
applications, a set of "pseudo-packages" could be created to alleviate the 
extra configuration requirements? 

I've previously used the DO_NOT_COMPILE option for the KDE ebuilds and 
successfully screened out many of the unwanted packages. If the dependencies 
for any given software application were known (herein lies the large amount 
of maintenance), it should then be possible to manipulate that environment 
variable to only compile what is necessary for the user. Granted it would 
take a fair amount of script-work, however it's an option to consider.


> And most people do want the whole of kde.

Unfortunately, I don't fall into the category of "most people" when it comes 
to KDE's software; the above comment is a prime example of why I migrated to 
Gentoo and Linux as opposed to windows.


-- 
Anthony Gorecki
Ectro-Linux Foundation


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

  reply	other threads:[~2004-09-18 18:04 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
2004-09-18 18:02   ` Anthony Gorecki [this message]
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=200409181103.01872.anthony@ectrolinux.com \
    --to=anthony@ectrolinux.com \
    --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