unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Yoshinori Arai <kumagusu08@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 34283@debbugs.gnu.org
Subject: [bug#34283] [PATCH] Add: mypaint
Date: Tue, 5 Feb 2019 18:23:05 +0900	[thread overview]
Message-ID: <20190205092305.v3nn5dj367udgrby@WaraToNora> (raw)
In-Reply-To: <87d0o6aiiz.fsf@gmail.com>

On Tue, Feb 05, 2019 at 12:52:52AM -0500, Maxim Cournoyer wrote:
> Hello Yoshinori!
> 
> Yoshinori Arai <kumagusu08@gmail.com> writes:
> 
> > Hello,
> >
> > I made mypaint package from git version.
> > libmypaint-git, mypaint-brushes-git may be conflict with gimp package.
> 
> In Guix, we can have multiple versions of the software without changing
> its name (it's one of the advantages of a functional package manager
> :-).  In general, we package the latest release available from
> upstream, unless there is a good justification to do otherwise.
> 
> Was there a reason to prefer the git snapshots over normal releases of
> mypaint, libmypaint and mypaint-brushes in Guix? I see that the latest
> release for mypaint-brushes was released only a couple days ago (2.0.1);
> unless there is a reason, it would be preferable to use this tagged
> released rather than some random commit.
> 
> In this case, since it seems the only dependent of mypaint is Gimp and
> since Gimp requires a specific version, (its configure.ac [0] mentions
> mypaint-brusesh 1.3.0, although Arch seems to work around it [1]), I'd
> go with a public variable named mypaint-brushes-2 for the new
> definition, leaving the current one in (gnu packages gimp) alone, thus
> not impacting Gimp. The name field of both packages should be the same,
> though, so that a user of mypaint-brushes can select the version as in:
> 
> guix package -i mypaint-brushes@2
> 
> I'd also put the new package definitions at the current location (gnu
> packages gimp) so that their different versions live in the same Guile
> module.
> 
> [0]  https://gitlab.gnome.org/garyskeete/gimp/blob/GIMP_2_10_4/configure.ac#L73
> [1]  https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mypaint-brushes-git
 
> I managed to make it run a couple of times, but then it started
> complaining about icons (even though I was adding the hicolor-icon-theme
> to my test environment). I also tried running fc-cache -vf, but in
> vain. Any ideas?
> 
> Thank you!
> 
> Maxim

Hello,

I will try to make patch of mypaint@1.3.0 in gimp package at first.

  reply	other threads:[~2019-02-05  9:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02  4:44 [bug#34283] [PATCH]Add: mypaint Yoshinori Arai
2019-02-05  5:43 ` swedebugia
2019-02-05  5:52 ` [bug#34283] [PATCH] Add: mypaint Maxim Cournoyer
2019-02-05  9:23   ` Yoshinori Arai [this message]
2019-02-05 11:42 ` [bug#34283] [PATCH]Add: mypaint Björn Höfling
2019-02-06 11:03   ` Yoshinori Arai
2019-02-07 11:13   ` Yoshinori Arai
2019-02-10 19:57     ` Danny Milosavljevic
2019-02-10 22:15       ` Yoshinori Arai
2019-02-08  4:26   ` Yoshinori Arai
2019-02-08  4:30     ` Brett Gilio
2019-02-09 22:54       ` Yoshinori Arai
2019-02-10  1:24         ` Brett Gilio
2019-02-10  2:36           ` Yoshinori Arai
2019-02-08  7:22 ` [bug#34283] [PATCH-1/4]Add: mypaint@1.2.1 Yoshinori Arai
2019-06-28  5:34   ` swedebugia
2019-02-08  7:24 ` [bug#34283] [PATCH-2/4]Add: libmypaint@2.0.0-alpha Yoshinori Arai
2019-02-08  7:25 ` [bug#34283] [PATCH-3/4]Add: mypaint-blushes@2.0.1 Yoshinori Arai
2019-02-08  7:27 ` [bug#34283] [PATCH-4/4]Add: mypaint@2.0.0-alpha.2 Yoshinori Arai
2021-01-15 19:50 ` bug#34283: [PATCH]Add: mypaint Julien Lepiller

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=20190205092305.v3nn5dj367udgrby@WaraToNora \
    --to=kumagusu08@gmail.com \
    --cc=34283@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).