From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libexif-0.6.22-1
Date: Thu, 31 Dec 2020 16:44:20 +0100 [thread overview]
Message-ID: <efb8c9af-8e8f-9051-5a46-aed2230b53a8@gmail.com> (raw)
In-Reply-To: <20201231195443.4EBD.50F79699@gmail.com>
On 31.12.2020 11:54, Lemures Lemniscati via Cygwin-apps wrote:
> Helped by Achim Gratz, now I can tell ITA for libexif-0.6.22-1 again,
> and, in a following mail, ITA for exif-0.6.22-1.
>
> --
> ITA for libexif, which has been maintained by Yaakov [1].
>
> Now, the latest upstream of libexif is 0.6.22 [2].
>
> A new candidate cygport file is placed at [3].
> And, it's been tested on Cygwin AppVeyor CI (ID 1557: [4]).
>
> Generated package files are placed at [5] and [6]:
>
> * libexif-common-0.6.22-1.tar.xz
> * libexif-devel-0.6.22-1.tar.xz
> * libexif12-0.6.22-1.tar.xz
>
> * libexif-0.6.22-1-src.tar.xz
> * libexif-debuginfo-0.6.22-1.tar.xz
it builds fine and pass the tests
I would remove the pull for the shared lib
printf -v "libexif${ABI}_REQUIRES" "%s" "libexif-common"
of the general doc
>>> libexif-common-0.6.22-1.tar.xz
usr/share/doc/
usr/share/doc/libexif/
usr/share/doc/libexif/ABOUT-NLS
usr/share/doc/libexif/AUTHORS
usr/share/doc/libexif/ChangeLog
usr/share/doc/libexif/COPYING
usr/share/doc/libexif/NEWS
usr/share/doc/libexif/README
usr/share/doc/libexif/SECURITY.md
but it is just my opinion
> Regards,
>
> Lem
>
GTG
Thanks & Regards
Marco
next prev parent reply other threads:[~2020-12-31 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 23:33 Lemures Lemniscati
2020-12-31 2:07 ` Lemures Lemniscati
2020-12-31 8:04 ` Lemures Lemniscati
2020-12-31 8:44 ` Achim Gratz
2020-12-31 8:49 ` Achim Gratz
2020-12-31 9:32 ` Lemures Lemniscati
2020-12-31 10:54 ` Lemures Lemniscati
2020-12-31 15:44 ` Marco Atzeri [this message]
2020-12-31 22:22 ` Lemures Lemniscati
2021-01-02 22:13 ` Achim Gratz
2021-01-03 2:46 ` Lemures Lemniscati
2021-01-03 3:22 ` Marco Atzeri
2021-01-03 9:51 ` Achim Gratz
2021-01-04 13:58 ` Lemures Lemniscati
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=efb8c9af-8e8f-9051-5a46-aed2230b53a8@gmail.com \
--to=marco.atzeri@gmail.com \
--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).