From: Milos Komarcevic <miloskomarcevic@aim.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Package request libinih & libinih-devel
Date: Fri, 6 Jan 2023 14:25:06 +0000 (UTC) [thread overview]
Message-ID: <1159210716.4656599.1673015106676@mail.yahoo.com> (raw)
In-Reply-To: <1159210716.4656599.1673015106676.ref@mail.yahoo.com>
On Fri, 6 Jan 2023 at 11:09, Lemures Lemniscati wrote:
> Hi,
>
> I've tried to build exiv2 from the upstream repository [1]
> with Adam's libinih package.
Thanks Lem for testing, I think this gives Adam the green light.
Adam, indeed this is a very small library and I presume will not increase its overhead in the future. I guess it's up to you whether to split it into the runtime and -devel packages as usual... Thank you very much for volunteering to maintain this package!
> Weirdly, this version [1] yields ./bin/cygexiv2-0.dll,
> while the current version v0.27.5 [2] yields ./bin/cygexiv2-27.dll.
>
> I guess this change is not intended, but I don't know how to fix it.
Yeah, it's a known issue on the main branch coming from this line of code:
https://github.com/Exiv2/exiv2/blob/842ef05ee60bff765c0402a211971aed53b728cc/src/CMakeLists.txt#L168
and the fact that the main branch has an arbitrary version set to 1.0.0 for now...
It shouldn't be related to anything discussed here though.
Best regards,
Milos
next parent reply other threads:[~2023-01-06 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1159210716.4656599.1673015106676.ref@mail.yahoo.com>
2023-01-06 14:25 ` Milos Komarcevic [this message]
2023-01-07 1:05 ` Lemures Lemniscati
[not found] <827312549.3990743.1672921877783.ref@mail.yahoo.com>
2023-01-05 12:31 ` miloskomarcevic
2023-01-05 13:49 ` Adam Dinwoodie
2023-01-06 11:09 ` 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=1159210716.4656599.1673015106676@mail.yahoo.com \
--to=miloskomarcevic@aim.com \
--cc=cygwin@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).