From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: [ITA] libmypaint
Date: Mon, 25 May 2020 19:12:00 -0400 [thread overview]
Message-ID: <2f56afec-1c12-2e25-d348-9b32e8e4e77b@cornell.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
cygport file attached.
The only notable change from Yaakov's cygport file is that upstream has changed
their library versioning scheme. Previously the DLL was cygmypaint-1-3-0.dll
and the library package was called libmypaint1.3_0. Now the DLL is
cygmypaint-0.dll, so I've called the library package libmypaint0.
This was a deliberate change, with much upstream discussion, so I don't think I
should mess with it.
Ken
[-- Attachment #2: libmypaint.cygport --]
[-- Type: text/plain, Size: 881 bytes --]
NAME="libmypaint"
VERSION=1.6.1
RELEASE=1
CATEGORY="Libs"
SUMMARY="MyPaint brush library"
DESCRIPTION="This is the brush library used by MyPaint. A number of other
painting programs use it too."
HOMEPAGE="https://github.com/mypaint/libmypaint"
SRC_URI="https://github.com/mypaint/libmypaint/releases/download/v${VERSION}/libmypaint-${VERSION}.tar.xz"
BUILD_REQUIRES="\
gobject-introspection \
libglib2.0-devel \
libjson-c-devel \
"
PKG_NAMES="libmypaint0 libmypaint-common libmypaint-devel girepository-MyPaint1.6"
libmypaint0_REQUIRES="libmypaint-common"
libmypaint0_CONTENTS="
usr/bin/cygmypaint-0.dll
"
libmypaint_common_CONTENTS="
usr/share/doc/${NAME}
usr/share/locale/*/*/libmypaint.mo
"
libmypaint_devel_CONTENTS="
usr/include/libmypaint/
usr/lib/libmypaint.dll.a
usr/lib/pkgconfig/libmypaint.pc
"
girepository_MyPaint1_6_CONTENTS="usr/*/gir*-1.0/MyPaint-1.6.*"
next reply other threads:[~2020-05-25 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 23:12 Ken Brown [this message]
2020-05-26 15:42 ` Marco Atzeri
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=2f56afec-1c12-2e25-d348-9b32e8e4e77b@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.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.
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).