public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] openh264 (2.3.1)
Date: Thu, 23 Feb 2023 12:54:04 +0000	[thread overview]
Message-ID: <ffcf89cc-8a53-29c6-4c00-acacd85f8a4e@dronecode.org.uk> (raw)
In-Reply-To: <20230222123308.5d171a96c957cc5be9eb2500@nifty.ne.jp>

On 22/02/2023 03:33, Takashi Yano via Cygwin-apps wrote:
> On Tue, 21 Feb 2023 14:11:46 +0000
> Jon Turney wrote:
>> On 20/02/2023 08:55, Takashi Yano via Cygwin-apps wrote:
>>> On Sun, 19 Feb 2023 15:37:47 +0000
>>> Jon Turney wrote:
>> [...]>> * I don't think you should need:
>>>>
>>>>> 	# Install postinstall/preremove scripts
>>>>> 	mkdir -p ${D}/etc/postinstall  ${D}/etc/preremove
>>>>> 	cp ${C}/lib${NAME}.postinstall ${D}/etc/postinstall/lib${NAME}.sh
>>>>> 	cp ${C}/lib${NAME}.preremove ${D}/etc/preremove/lib${NAME}.sh
>>>>>
>>>>
>>>> This should happen automatically if the files are in $C (and you can
>>>> list them in CYGWIN_FILES or make them with cygwin.patch file to put
>>>> them there)
>>>
>>> That's what I understood from
>>> https://cygwin.github.io/cygport/masterindex.html,
>>> however, actually libopenh264.{postinstall,preremove} are
>>> not installed during install process by cygport 0.36.0
>>> even though openh264-2.3.1-1.cygwin.patch exists.
>>>
>>> Could you please give me a hint how I can make it work?
>>
>> Aha! This is a bug in cygport.
>>
>> (There's some code which skips over doing this for the first item in
>> PKG_NAMES, assuming that is always the same as PN, which has already
>> been done)
>>
>> Thanks for drawing that to my attention. I'll look into fixing it, but
>> for the moment it seems you can workaround the bug by ensuring that the
>> package with premove/postinstall scripts isn't first in that list, i.e.:
>>
>> - PKG_NAMES="libopenh264 libopenh264-headers"
>> + PKG_NAMES="libopenh264-headers libopenh264"
> 
> Thanks! It works.
> 
> I updated the cygport file and cygwin.patch.

GTG.


  reply	other threads:[~2023-02-23 12:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  8:37 Takashi Yano
2023-02-05 16:36 ` Jon Turney
2023-02-06 12:22   ` Takashi Yano
2023-02-06  2:44 ` Yaakov Selkowitz
2023-02-06  5:11   ` Brian Inglis
2023-02-06  5:16     ` Yaakov Selkowitz
2023-02-06  5:25       ` Takashi Yano
2023-02-09 12:02         ` Takashi Yano
2023-02-10  4:35         ` Yaakov Selkowitz
2023-02-10  5:05           ` Takashi Yano
2023-02-10  5:18             ` Takashi Yano
2023-02-10  5:25               ` Takashi Yano
2023-02-13 18:30                 ` Jon Turney
2023-02-13 19:03                   ` Brian Inglis
2023-02-14  9:11                     ` Takashi Yano
2023-02-14 11:02                       ` ASSI
2023-02-14 12:28                         ` Takashi Yano
2023-02-14 16:41                           ` ASSI
2023-02-14 21:21                             ` Takashi Yano
2023-02-16 19:24                               ` Jon Turney
2023-02-17  8:49                                 ` Takashi Yano
2023-02-19 15:37                                   ` Jon Turney
2023-02-20  8:55                                     ` Takashi Yano
2023-02-21 14:11                                       ` Jon Turney
2023-02-22  3:33                                         ` Takashi Yano
2023-02-23 12:54                                           ` Jon Turney [this message]
2023-02-24  9:16                                             ` Takashi Yano
2023-02-06 22:40       ` Lee
2023-02-07  5:19       ` Brian Inglis

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=ffcf89cc-8a53-29c6-4c00-acacd85f8a4e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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).