From: R Veera Kumar <vkor@vkten.in>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 40281@debbugs.gnu.org
Subject: [bug#40281] [PATCH v2] gnu: Add mtpaint.
Date: Fri, 3 Apr 2020 10:12:51 +0530 [thread overview]
Message-ID: <20200403044251.GA1591@tulip> (raw)
In-Reply-To: <87k12xw6f6.fsf@elephly.net>
On Fri, Apr 03, 2020 at 06:15:57AM +0200, Ricardo Wurmus wrote:
>
> R Veera Kumar <vkor@vkten.in> writes:
>
> > * gnu/packages/image.scm (mtpaint): New variable.
>
> Thank you for the patch!
>
> > +
> > +(define-public mtpaint
> > + (let ((commit "03b1b0938067b88d86d9f1b1088730f1934d411e")
> > + (revision "1"))
>
> Why is this particular commit needed? Can’t we use the latest release?
>
The author does not make release tarballs or even make git release tags.
He only puts package version in git commit title.
> > + (package
> > + (name "mtpaint")
> > + (version (git-version "3.49.25" revision commit))
> > + (source
> > + (origin
> > + (method git-fetch)
> > + (uri (git-reference
> > + (url "https://github.com/wjaguar/mtPaint/")
> > + (commit commit)))
> > + (file-name (git-file-name name version))
> > + (sha256
> > + (base32 "0izm2wvj26566fd8mqvypr7bmv7jnq8qhp4760m7z2wrc4y8pjn1"))))
> > + (build-system gnu-build-system)
> > + (native-inputs
> > + `(("gettext" ,gettext-minimal)
> > + ("pkg-config" ,pkg-config)
> > + ("pkg-config" ,pkg-config)
>
> You have this line twice.
>
Will correct this.
> > + ("which" ,which)))
> > + (inputs
> > + `(("imlib2" ,imlib2)
> > + ("libtiff" ,libtiff)
> > + ("libpng" ,libpng)
> > + ("libungif", libungif)
> > + ("libjpeg", libjpeg)
> > + ("libwebp" ,libwebp)
> > + ("openjpeg" ,openjpeg)
> > + ("lcms" ,lcms)
> > + ("zlib", zlib)
> > + ("glib" ,glib)
> > + ("gtk+" ,gtk+-2)))
>
> Could you please build with gtk+ (i.e. version 3). You probably need to
> add “gtk3” to the configure flags.
>
Currently gtk2 support is stable. gtk3 is testing stage.
> > + (arguments
> > + `(#:configure-flags
> > + (list
> > + "intl") ;; internationalized support
>
> Please remove the line break.
> For margin comments (at the end of a line) use just one semicolon please.
>
Will correct.
> > + ;; no check target
> > + #:tests? #f))
> > + (home-page "http://mtpaint.sourceforge.net/")
> > + (synopsis "Create pixel art and manipulate digital images")
> > + (description
> > + "Mtpaint is a graphic editing program which uses the GTK+ toolkit.
> > +It can create and edit indexed pallete or 24bit RGB images, offers
> > basic
>
> “pallete” –> “palette”
>
Will correct.
> > +painting and palette manipulation tools.
>
> Same here.
>
Will correct.
R Veera Kumar
> --
> Ricardo
next prev parent reply other threads:[~2020-04-03 4:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 17:21 [bug#40281] [PATCH] gnu: Add mtpaint R Veera Kumar
2020-03-31 9:39 ` [bug#40281] [PATCH v2] " R Veera Kumar
2020-04-03 4:15 ` Ricardo Wurmus
2020-04-03 4:42 ` R Veera Kumar [this message]
2020-04-03 16:33 ` [bug#40281] [PATCH v3] " R Veera Kumar
2020-04-04 17:33 ` [bug#40281] [PATCH v4] " R Veera Kumar
2020-04-05 17:48 ` bug#40281: " Danny Milosavljevic
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=20200403044251.GA1591@tulip \
--to=vkor@vkten.in \
--cc=40281@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).