all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Krita 3 and 4 compatibility issues
Date: Thu, 22 Mar 2018 20:04:34 +0100	[thread overview]
Message-ID: <89acd489-c3c1-0061-cc9d-4d3f763fe941@freenet.de> (raw)
In-Reply-To: <20180322174457.GA8888@jasmine.lan>

On 22.03.2018 18:44, Leo Famulari wrote:
> I updated Krita to 4.0.0, but later I noticed some issues with the
> transition, notably that the Krita 3 and 4 file formats are not totally
> compatible and may not work consistently between versions:

> Should we do anything about this?


In this specific case, you may bet on a very low number of users of 
Krita via guix, all of whom are likely to be enthusiastic enough to get 
such news right from the source.

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.

In general, though, it points to a need of bringing such messages to 
users attention. On first startup of the new application version would 
be a bit on the disruptive side and without a unified desktop 
environment, one has to wonder how it could be done technically, anyway.

There should be a clear answer to a user's question of what the last 
update brought them, though.


-- 
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/

  reply	other threads:[~2018-03-22 19:07 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 [this message]
2018-03-23 15:06   ` ng0
2018-03-23 19:34     ` Leo Famulari

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=89acd489-c3c1-0061-cc9d-4d3f763fe941@freenet.de \
    --to=t_w_@freenet.de \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.