DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 452EvrSf3418112
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=x6iHRQwh
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B24AE38A240D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1717340272;
	bh=9ExT++SQStE1XdtRHbWqZ0VMu6SabZaQPg44Q0CYluQ=;
	h=Date:Subject:To:References:Cc:In-Reply-To:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=x6iHRQwhFEG16faAKaEq7mlrp1FxMKe3bPvuz82scjjIaL6ZXHypxwmEkyepuiOIi
	 W3/3YLmLZkgTeSOih5QPHJ0Je3iCVY9gMik0dZHGavcIlznHacYrDzvi67/Ppj/ZdG
	 6axhs1oJ8UYoammZB8F70yxEn5xWxokRVKtAvO4U=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A0C8D38102A5
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org A0C8D38102A5
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1717340213; cv=none;
 b=G7VeE+FGh6sicVPDSrpaELnwX2e9uK3SMy6quUXokazJYmMcL9l1N3tEjYM3s0Uiy8UEYkt2f0957Bio3mJxzsH5xFoM6VxszzD1y4yE26OE1jGUVZu61ZRUNoa1LObxswydU8HPsSKtC3W6Ca0wpgSkDSJAZl+NY4N5/+QlFzU=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1717340213; c=relaxed/simple;
 bh=3CVo0P2d9hhnxaDOfvNW3Lef8hQOd5lBwJOni940knA=;
 h=Message-ID:Date:MIME-Version:Subject:To:From;
 b=tnuy3JpjiaW1Gc4yny3N31FvVr+lA/e619X4eba14t5JHuP7QeUHbJM0X9MZR4VCXnYbS8kLzy8CQXM2TlpSoYhuW577dAXw3AhDAhQzz/rS/f8es/dIIFkqihkHtk6k5P8V7BkChRDMzmH6gOpEeIxSxlZOn5EY7pdETBY2lEw=
ARC-Authentication-Results: i=1; server2.sourceware.org
X-SNCR-Rigid: 65A567CD0FB56407
X-Originating-IP: [86.139.167.83]
X-OWM-Source-IP: 86.139.167.83
X-OWM-Env-Sender: jon DOT turney AT dronecode DOT org DOT uk
X-VadeSecure-score: verdict=clean score=0/300, class=clean
X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvledrvdeltddgkedvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfevjggtgfesthekredttddvjeenucfhrhhomheplfhonhcuvfhurhhnvgihuceojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukheqnecuggftrfgrthhtvghrnhepiefhieffleefffetgeetheevueduieektdevgfejgeeiieefgeetkeekieetkeffnecuffhomhgrihhnpegthihgfihinhdrtghomhdpghhithhhuhgsrdgtohhmnecukfhppeekiedrudefledrudeijedrkeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddutdelngdpihhnvghtpeekiedrudefledrudeijedrkeefpdhmrghilhhfrhhomhepjhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhdpnhgspghrtghpthhtohepvddprhgtphhtthhopegthihgfihinhdqrghpphhssegthihgfihinhdrtghomhdprhgtphhtthhopegthihgfihinhestgihghifihhnrdgtohhmpdhrvghvkffrpehhohhsthekiedqudefledqudeijedqkeefrdhrrghnghgvkeeiqddufeelrdgsthgtvghnthhrrghlphhluhhsrdgtohhmpdgruhhthhgp
 uhhsvghrpehjohhnthhurhhnvgihsegsthhinhhtvghrnhgvthdrtghomhdpghgvohfkrfepifeupdfovfetjfhoshhtpehsrgdqphhrugdqrhhgohhuthdqtddtvd
X-RazorGate-Vade-Verdict: clean 0
X-RazorGate-Vade-Classification: clean
Message-ID: <db4e384c-bf3c-4e01-ac3a-9db342be1548@dronecode.org.uk>
Date: Sun, 2 Jun 2024 15:56:45 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: newer version of mingw64-*-win-iconv ?
To: Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
References: <4642707 DOT lMtyQzBqa6 AT nimes>
 <86d93340-5f12-40e7-b285-7ad9137b796c AT SystematicSW DOT ab DOT ca>
Content-Language: en-US
Cc: cygwin-apps AT cygwin DOT com
In-Reply-To: <86d93340-5f12-40e7-b285-7ad9137b796c@SystematicSW.ab.ca>
X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00, BODY_8BITS,
 JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_PASS,
 TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Jon Turney via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 452EvrSf3418112

On 29/05/2024 07:58, Brian Inglis via Cygwin wrote:
> On 2024-05-28 19:12, Bruno Haible via Cygwin wrote:
>> It would be useful if someone could rebuild the two packages
>>    https://cygwin.com/packages/summary/mingw64-i686-win-iconv.html
>>    https://cygwin.com/packages/summary/mingw64-x86_64-win-iconv.html
>> based off the current git HEAD [1].
>> Reason: The current git HEAD is a reasonable alternative to
>> GNU libiconv; all encodings that it supports, other than EUC-JP
>> and GB18030, have reasonably good conversion tables. Wherease the
>> current Cygwin packages are based off source code from 2013
>> and have a major problem already with the ASCII encoding.
>> [1] https://github.com/win-iconv/win-iconv
> 
> Ran playground local and CI builds of these packages at v0.0.8 
> successfully:
> 
>      https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=mingw64-x86_64-win-iconv
> 
>      https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=mingw64-x86_64-win-iconv
> 
> Do we really need the fix at git HEAD to add UCS-2-INTERNAL encoding?
> 
> Could someone please do any further tweaks for this source git if 
> required, and do NMU builds and deploys of these?

I've given you NMU privileges, so now that someone can be you!


> [Are we really still building 32 bit mingw packages when we dropped 
> support of 32 bit Windows << 1%?

There's a difference between "we don't support running on 32-bit 
Windows" and "We don't support cross-compiling to 32-bit Windows".

Now, I'd like to do this in an evidence based manner e.g. if we had some 
statistics on packages that cygwin users choose to install, and hardly 
anyone was bothering with mingw 32-bit packages, then dropping them 
would be a good way of conserving our very limited maintainer resource.

But as previously observed, that depends on building something to 
collect that data, which SHTDI.

(There's also some unfinished work by Yaakov in a branch of the cygport 
repo which enhances cross-compile support, so that a single source 
package can produce mingw-cross install packages for multiple 
architectures, which would make it easier to continue to support these 
packages, and/or drop them in future, and/or add mingw arm64 
cross-packages when the toolchain for them exists...)


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple