From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Krita 3 and 4 compatibility issues Date: Fri, 23 Mar 2018 15:34:44 -0400 Message-ID: <20180323193444.GC15671@jasmine.lan> References: <20180322174457.GA8888@jasmine.lan> <89acd489-c3c1-0061-cc9d-4d3f763fe941@freenet.de> <20180323150652.42yoxpfclsu2l56j@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8NvZYKFJsRX2Djef" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ezSSf-00053l-7O for guix-devel@gnu.org; Fri, 23 Mar 2018 15:34:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ezSSc-00074Z-1E for guix-devel@gnu.org; Fri, 23 Mar 2018 15:34:49 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:60687) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ezSSb-00073x-Sw for guix-devel@gnu.org; Fri, 23 Mar 2018 15:34:45 -0400 Content-Disposition: inline In-Reply-To: <20180323150652.42yoxpfclsu2l56j@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Thorsten Wilms , guix-devel@gnu.org --8NvZYKFJsRX2Djef Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 23, 2018 at 03:06:52PM +0000, ng0 wrote: > Thorsten Wilms transcribed 1.2K bytes: > > A short note regarding the option to keep both Krita 3 and 4 accessible > > would be nice in this and any future similar case. The likelihood of not > > working in the same profile, potential configuration clashes, the optio= n to > > use different profiles or guix environment, as you mentioned on #guix. >=20 > I agree, in this case having Krita 3 and 4 available helps. We could defa= ult > to 4 but keep 3 available for downgrading to it. I think we could keep both Krita 3 and 4 around for a while, removing the older one in a few months. It's easy with a package like this: (define-public krita-3 (package (inherit krita) (name "krita") (version "3.3.3") (source (origin (inherit (package-source krita)) (uri (string-append "mirror://kde/stable/krita/" (version-prefix version 3) "/" name "-" version ".tar.gz")) (sha256 (base32 "0pc6hnakkqy81x5b5ncivaps6hqv43i50sjwgi3i3cz9j8rlxh5y")))))) --8NvZYKFJsRX2Djef Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlq1VtMACgkQJkb6MLrK fwj0lBAA2gM8bWIRFubn9GTHswbVJ6manY+nD3tWivG9SJITsHjgBOl3feOxnRoY qvIQYgHwKwBmKpeclmCe28qKdTj+nnSUYBnplHUZDuORt0BEAG5biN/BAK4fWeEf 3hkKuXixhxMKOYpTghlbvzAjovLmCh9sg7z/4ye7EHTCivZctumRxKgYeYkglxFt M7aoh0qWzG19GpNuHpfi8/SCDNaKfqYOE9kWtaWwiLeucU3HzQHewrcZOLs6gFo/ KtlePCCRckGHiNMWk98NAQzfwDmar2OFWB71+bE4cznDl5EMRV3FcvNTtYFBuOGK clgUaOAYf0Pb4n6ECClyWyOkKx0Uy20YVGz3mdFtJTqDnmzlIeDzFZpUXiv57qrK YAMgEFyjSrOHDqTVIGmkJNi1U6TCaWAyqw4/sWmWDvjA72jHXjAhMulPD3bXYhzD RFqWekTmLvmcXrYL8kdOW0wl4XdYlLs9ShQ/dFUdTR07TggbA/qd/s2LM26QxGVl ELCLyf4waMWGkV6TXgfA5iGY3Q//SVLsGHWTj3EsLzZsrPXVC64LHaK29l6NCROt o8aaInG0TAlpOfIvEGS9q4L3hzuE5SRT4s5rimcJrnijoampJCO6Fh4TnovpNvIZ T+ucOhYqrM8NhJt18Zs1SAsAMrNi/ZV4Z6jkAPN1ioDFcHSgK78= =PBLb -----END PGP SIGNATURE----- --8NvZYKFJsRX2Djef--