public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev]  Re: [RFC] portage-2.1.6 release plans
Date: Sat, 8 Nov 2008 09:32:28 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.11.08.09.32.27@cox.net> (raw)
In-Reply-To: 4914E580.5010502@gentoo.org

Zac Medico <zmedico@gentoo.org> posted 4914E580.5010502@gentoo.org,
excerpted below, on  Fri, 07 Nov 2008 17:04:00 -0800:

> I haven't talked to [the kde project] about [hard-masking all portage 
versions with set support] but AFAIK it entirely possible to use
> kde4 without package sets since the meta-ebuilds are available.

Hmm... I followed the kde4 guide, which talks about sets, and was under 
the impression they either weren't even doing the metapackages, with sets 
supplanting them, of if they were, they were using set dependencies, thus 
required sets.

A quick look demonstrates that impression was wrong, however.  I'd never 
even checked to see if the meta-ebuilds were actually there!

So... it seems the ebuilds are there.  Never-the-less, for folks who have 
followed the kde4 guide, sets will be (almost) a must, since that's what 
it talks about using, so that's probably what folks who read the guide 
/did/ use.  I know it's what I used.[1]

Regardless, I'd definitely touch base with them on it.  At minimum, the 
upgrade guide will need either changed or taken down, if set support goes 
back hard-masked.  I doubt they'll be very happy about it, but if it 
needs to happen, well...

[1] FWIW, I have kde-4.1.2 merged, but consider it still broken and well 
short of what I'd find actually workable for daily use.  There's just too 
many bits and pieces that don't work, and won't work until at least 
4.2.0, possibly 4.3.0 the way things are going.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2008-11-08  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 23:38 [gentoo-portage-dev] [RFC] portage-2.1.6 release plans Zac Medico
2008-11-08  0:45 ` [gentoo-portage-dev] " Duncan
2008-11-08  1:04   ` Zac Medico
2008-11-08  9:32     ` Duncan [this message]
2008-11-08 17:33       ` Zac Medico
2008-11-08  5:28 ` [gentoo-portage-dev] " Marius Mauch
2008-11-08  5:46   ` Zac Medico

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=pan.2008.11.08.09.32.27@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-portage-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