From: Leo Famulari <leo@famulari.name>
To: L p R n d n <guix@lprndn.info>
Cc: 40214@debbugs.gnu.org
Subject: [bug#40214] [PATCH 1/4] gnu: libmypaint: Update to 1.5.1.
Date: Thu, 30 Apr 2020 17:42:30 -0400 [thread overview]
Message-ID: <20200430214230.GA833@jasmine.lan> (raw)
In-Reply-To: <87zhasn0cp.fsf@lprndn.info>
On Thu, Apr 30, 2020 at 11:13:26PM +0200, L p R n d n wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Thu, Apr 30, 2020 at 07:12:23PM +0200, L p R n d n wrote:
> >> Here are the updated patches. First patch moves libmypaint and
> >> mypaint-brushes to a new drawing.scm file, second adds mypaint.
> >
> > I'm not sure about adding a module (gnu packages drawing). The software
> > that could fit there can generally also be used for "painting",
> > "drafting", "photography post-production", and other activities of a
> > visual nature.
> >
> > We already have image and graphics modules that are rather ambiguous.
> > How about one of those? Or creating a mypaint module?
>
> You're right! I didn't find image.scm when searching for the right
> place. Should I move libpaint and mypaint-brushes too? It feels weird to
> have them in a different place.
Yeah, now that we will have mypaint, it makes sense to keep them all
together :)
next prev parent reply other threads:[~2020-04-30 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 13:34 [bug#40214] [PATCH 1/4] gnu: libmypaint: Update to 1.5.1 Lprndn
2020-03-24 15:35 ` [bug#40214] [PATCH 2/4] gnu: mypaint-brushes: Update to 1.3.1 guix
2020-03-24 15:35 ` [bug#40214] [PATCH 3/4] gnu: Add mypaint-brushes-2 guix
2020-03-24 15:35 ` [bug#40214] [PATCH 4/4] gnu: Add mypaint guix
2020-04-29 19:48 ` [bug#40214] [PATCH 1/4] gnu: libmypaint: Update to 1.5.1 Leo Famulari
2020-04-30 17:12 ` L p R n d n
2020-04-30 17:48 ` Leo Famulari
2020-04-30 21:13 ` L p R n d n
2020-04-30 21:42 ` Leo Famulari [this message]
2020-05-01 10:40 ` L p R n d n
2020-05-01 21:05 ` Leo Famulari
2020-05-02 8:09 ` L p R n d n
2020-05-02 22:40 ` L p R n d n
2020-12-08 20:11 ` bug#40214: " Christopher Baines
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=20200430214230.GA833@jasmine.lan \
--to=leo@famulari.name \
--cc=40214@debbugs.gnu.org \
--cc=guix@lprndn.info \
/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).