public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Once again baffled by portage
Date: Sat, 19 Jan 2008 16:01:49 +0100	[thread overview]
Message-ID: <200801191601.55583.bo.andresen@zlin.dk> (raw)
In-Reply-To: <200801181636.29275.alan.mckinnon@gmail.com>

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

On Friday 18 January 2008 15:36:29 Alan McKinnon wrote:
> > > Roll on KDE4 when this monolithic nonsense will go away and there
> > > will only be -meta ebuilds.
> >
> > Actually it was decided to keep monolithics in KDE 4.0.0. Splits are
> > now the default which means they are listed first in any-of
> > dependency blocks such as e.g. || ( kde-base/kompare:kde-4
> > kde-base/kdesdk:kde-4 ) in KDE 4. But monos are still around. There
> > is a list of the monos in the url I posted in another mail to this
> > thread.
>
> Interesting, I wasn't aware of that. Obviously my most current info is
> out of date.
>
> But why was that decision taken? I understand keeping it for kde-3.5.x
> users, but kde-4 is essentially an entirely different product, and
> the -meta ebuilds do everything the monolithic ones ever did. The
> configure steps do add time though, but other than that everything
> seems to work the same

Well, it wasn't really my decision. ;) But I can say that a pro is that it 
provides the users with a choice and the maintainance overhead when compared 
to only doing splits isn't really all that big. The only real con in my 
opinion is that it confuses those who haven't read the kde-split document 
before installing kde.

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-19 15:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 15:28 [gentoo-user] Once again baffled by portage Grant Edwards
2008-01-17 15:52 ` [gentoo-user] " Michael Schmarck
2008-01-17 16:00 ` Guilherme Amadio
2008-01-17 16:06 ` [gentoo-user] " Alan McKinnon
2008-01-17 19:47   ` [gentoo-user] " Grant Edwards
2008-01-17 20:20     ` Alan McKinnon
2008-01-17 23:41   ` [gentoo-user] " Bo Ørsted Andresen
2008-01-18  0:08     ` Neil Bothwick
2008-01-18  0:17       ` Bo Ørsted Andresen
2008-01-18  1:04         ` Neil Bothwick
2008-01-18 14:36     ` Alan McKinnon
2008-01-19 15:01       ` Bo Ørsted Andresen [this message]
2008-01-17 19:50 ` Bo Ørsted Andresen

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=200801191601.55583.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --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