From: ng0 <ng0@n0.is>
To: Thorsten Wilms <t_w_@freenet.de>
Cc: guix-devel@gnu.org
Subject: Re: Krita 3 and 4 compatibility issues
Date: Fri, 23 Mar 2018 15:06:52 +0000 [thread overview]
Message-ID: <20180323150652.42yoxpfclsu2l56j@abyayala> (raw)
In-Reply-To: <89acd489-c3c1-0061-cc9d-4d3f763fe941@freenet.de>
Thorsten Wilms transcribed 1.2K bytes:
> 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.
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.
> 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/
>
--
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://n0.is
next prev parent reply other threads:[~2018-03-23 15:06 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 [this message]
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
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=20180323150652.42yoxpfclsu2l56j@abyayala \
--to=ng0@n0.is \
--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).