-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duncan wrote:
> Zac Medico <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
> 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.

There is no such thing as "set dependencies" yet. It would require a
new EAPI. I'm not sure that "set dependencies" are such a good idea,
mainly because of the way that users are allowed to subtract atoms
from sets. In practice, it's somewhat like package.provided, so a
"set dependency" wouldn't actually guarantee that all the intended
atoms from that set are installed.

> 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...

The worst case is that they'll have to unmask portage-2.2 if they
want to use sets instead of meta-ebuilds.

> [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.

I tried kde-4.1.2, using the kde-meta ebuild, when they first put it
in the tree. I wasn't comfortable with it so I use kde-3.5.x still.

- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkkVzV0ACgkQ/ejvha5XGaN5mwCePYo0lp9oFECPA5+CDTK81pWO
V+MAnRFBJKDtfBp4rSOWeeZkE0/ZUidW
=Uh78
-----END PGP SIGNATURE-----

Reply via email to