From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LTZTq-0003Lr-Mr for garchives@archives.gentoo.org; Sun, 01 Feb 2009 10:23:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 53BC6E03BC; Sun, 1 Feb 2009 10:23:09 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 1984DE03BC for ; Sun, 1 Feb 2009 10:23:09 +0000 (UTC) Received: from krikkit (krikkit.digimed.co.uk [192.168.1.3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id ADF3246602B for ; Sun, 1 Feb 2009 10:23:06 +0000 (GMT) Date: Sun, 1 Feb 2009 10:22:52 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] KDE-4.2 and KDE-3.5 Message-ID: <20090201102252.6aa7650f@krikkit> In-Reply-To: <1172072913.1415221233432552207.JavaMail.root@avocado.cs.athabascau.ca> References: <122318397.1415181233432347614.JavaMail.root@avocado.cs.athabascau.ca> <1172072913.1415221233432552207.JavaMail.root@avocado.cs.athabascau.ca> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.0cvs46 (GTK+ 2.14.7; i686-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/5F=lKi+_qdZGe/tDmQbQJ.q"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: dd2a82ed-b1cb-42f2-ab9f-9c79302fff46 X-Archives-Hash: 0958e927682d85e7cf9798119218a58b --Sig_/5F=lKi+_qdZGe/tDmQbQJ.q Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 31 Jan 2009 13:09:12 -0700 (MST), Dmitry Makovey wrote: > Now my question is: how safe is it to do a workaround, and create local > version of kde-base/kdelibs-4.2.0-r1 ebuild (say, -r2) which removes > the block and just stick with 3.5.9 on 3.5 side ? I really don't feel > like unmasking 3.5.10 builds and building them too. The devs put that block on for a reason. You are free to remove it safe in the knowledge that you can claim sole responsibility for all the broken pieces. This seems a lot more risky than running a well-tested ~arch package. > another confusing thing is: > !<=3Dkde-base/kdebase-3.5.9-r4 > !<=3Dkde-base/kdebase-startkde-3.5.10 > which I read as "you're fine using kde-3.5.9 as long as you don't use > startkde". kind of weird. Not at all. All versions of startkde older than 3.5.10-r1 cause a problem with KDE4. Using a more recent version or no version at all. Some people may have their own custom KDE startup scripts. --=20 Neil Bothwick Don't take life too seriously, you won't get out alive. --Sig_/5F=lKi+_qdZGe/tDmQbQJ.q Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmFeAEACgkQum4al0N1GQNPXACgztQnDHjXZ8EAqMEaGgNLYJFH wwcAn3s0mAPN+VqIj/rWEek31R0/Zr6H =hHgF -----END PGP SIGNATURE----- --Sig_/5F=lKi+_qdZGe/tDmQbQJ.q--