unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Thorsten Wilms <t_w_@freenet.de>, guix-devel@gnu.org
Subject: Re: Krita 3 and 4 compatibility issues
Date: Fri, 23 Mar 2018 15:34:44 -0400	[thread overview]
Message-ID: <20180323193444.GC15671@jasmine.lan> (raw)
In-Reply-To: <20180323150652.42yoxpfclsu2l56j@abyayala>

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

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 option to
> > use different profiles or guix environment, as you mentioned on #guix.
> 
> I agree, in this case having Krita 3 and 4 available helps. We could default
> 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"))))))

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-03-23 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 17:44 Krita 3 and 4 compatibility issues Leo Famulari
2018-03-22 19:04 ` Thorsten Wilms
2018-03-23 15:06   ` ng0
2018-03-23 19:34     ` Leo Famulari [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180323193444.GC15671@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=t_w_@freenet.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).