From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: gengetopt missing in x86 package search and x86 setup.ini
Date: Mon, 2 Aug 2021 11:45:55 -0600 [thread overview]
Message-ID: <09645ee6-f32a-dee7-038e-b030fbb7adcb@SystematicSw.ab.ca> (raw)
In-Reply-To: <28db5737-a049-6edb-4f13-13115b1842d0@SystematicSw.ab.ca>
On 2021-07-26 17:50, Brian Inglis wrote:
> On 2021-07-26 14:04, Marco Atzeri via Cygwin-apps wrote:
>> On 25.07.2021 22:35, Brian Inglis wrote:
>>> On 2021-05-18 18:32, Brian Inglis wrote:
>>>> On 2021-05-18 10:05, Marco Atzeri via Cygwin-apps wrote:
>>>>> On 18.05.2021 15:47, Brian Inglis wrote:
>>>>>> Needed dependency for libidn build missing from x86.
>>>>
>>>>> It seems Rafel has missed to note the need to build for
>>>>> both architectures.
>>>>
>>>> Ping Rafel Amer - need x86 gengetopt build please!
>>>
>>> Adding DM as no response within 2 months:
>>>
>>> Ping(2) Rafel Amer - need x86 gengetopt build please!
>>>
>>> If we don't get a response, I can build and install my own, but that
>>> does not help deploys, so what's the fallback plan?
>> 1) put you as co-maintainer
>> 2) we can directly upload in the proper directory
>>
>> 1 looks better, IMHO
> Good idea, let's wait a week, then if no response, I'll ask to do that
> with CC to Rafel.
> It looks in cygcheck-dep that only libidn and libidn2 depend on
> gengetopt, and I maintain the latter and hope soon to adopt the former,
> if I can get autoreconf autopoint downgrades resolved.
As we have had no response over the last few weeks from the current
official maintainer of gengetopt, Rafel Amer Ramon, and my Cygwin
packages are the only ones documented to have gengetopt as a dependency,
*please add me as co-maintainer of gengetopt,*
so I can upload x86 release.
We also appear to have downstream projects and app developers using the
package.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-08-02 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 13:47 Brian Inglis
2021-05-18 16:05 ` Marco Atzeri
2021-05-19 0:32 ` Brian Inglis
2021-07-25 20:35 ` Brian Inglis
2021-07-26 20:04 ` Marco Atzeri
2021-07-26 23:50 ` Brian Inglis
2021-08-02 17:45 ` Brian Inglis [this message]
2021-08-04 13:34 ` Jon Turney
2021-08-04 15:38 ` 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=09645ee6-f32a-dee7-038e-b030fbb7adcb@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).