public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] openexr and ilmbase
Date: Thu, 7 Jul 2022 18:59:50 +0100	[thread overview]
Message-ID: <d186ff9f-bcb1-8e74-8923-edd8572fd5f6@dronecode.org.uk> (raw)
In-Reply-To: <e1da8bcc-5af6-f2cb-4f79-b293a0aba958@gmail.com>

On 07/07/2022 06:35, Marco Atzeri wrote:
> latest version attached
> 
> On 07.07.2022 06:43, Marco Atzeri wrote:
>> Hi Guys,
>>
>> updating latest GDAL I noticed that one of the potential dependency 
>> was orphan.
>>
>> As the current upstream code of the two interlinked packages openexr and
>> ilmbase is currently merged I propose to do the same
>>
>> https://github.com/AcademySoftwareFoundation/openexr/tags
>>
>>
>> version 3 does not build, so for the time being, I will release the 
>> latest 2.5.8 version
>>
>> Attached cygport.
>> I am aware that not all tests pass cleanly

Thanks.  Looks good.

> libIlmImf2_25_26_DESCRIPTION="High dynamic-range image format"
> libIlmImf2_25_26_CONTENTS="
> usr/bin/cygIlmImf-2_5-26.dll
> usr/bin/cygIlmImfUtil-2_5-26.dll
> "

Except, why is this package not named 'libIlmImf2_5_26'? (cf. 
'libilmbase2_5_25')

> libilmbase_common_CONTENTS="usr/share/doc/"

Perhaps this package should be named 'something-doc' instead?

  reply	other threads:[~2022-07-07 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  4:43 Marco Atzeri
2022-07-07  5:35 ` Marco Atzeri
2022-07-07 17:59   ` Jon Turney [this message]
2022-07-07 19:06     ` 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=d186ff9f-bcb1-8e74-8923-edd8572fd5f6@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=marco.atzeri@gmail.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).