[ITA] iso-codes

Brian Inglis Brian.Inglis@SystematicSW.ab.ca
Fri Apr 18 20:06:56 GMT 2025


On 2025-04-18 12:12, Philippe Baril Lecavalier via Cygwin-apps wrote:
> My apologies for not noticing this in playground! I have ingested some
> of its enhancements over the original to produce a superior proposal.

Part of the learning process we all went through.
> Thanks for pointing to the playground branch. Didn't quite get what
> it's about at first, but as the CI listens to it, then it makes a lot
> of sense. Tests are not conclusive for now, issue with autoconf2.7
> (already raised in another thread).
> https://github.com/cygwin/scallywag/actions/runs/14536664205
> 
> One question, about proper usage here: If something is promoted from
> playground to master, do you merge branch or keep a  smooth history in
> master? I have the feeling that whatever commit is done in playground
> is meant to stay in playground, hence the name.

Depends on what you are doing in playground and the whether you want those 
changes propagated back into master?

If you are trying out stuff that is experimental, keep it in playground, but if 
you are working around issues and resolve it in playground, then clean it up, 
and merge the final tweak back into master, which gives it another CI run to 
check you did not do, or fail to do, something that would affect the build.

> On Thu, Apr 17, 2025 at 2:28 PM Brian Inglis via Cygwin-apps wrote:
>>
>> On 2025-04-16 08:35, Philippe Baril Lecavalier via Cygwin-apps wrote:
>>> iso-codes: 4.3 (2019) -> 4.18.0 (released this month)
>>>
>>> noarch, simple enough. Custom `src_compile` no longer needed. Built
>>> packages are the same size with or without this (and no such step in
>>> Gentoo ebuild). Must have been fixed in their build system at some
>>> point in time.
>>
>> ++
>>
>> Care to clone the repo https://cygwin.com/git/cygwin-packages/iso-codes.git,
>> change to the playground branch, and update the cygport, where I did a couple of
>> commits for an NMU proposal to 4.9 a few years ago that went nowhere, and do a
>> push to run a CI build (any maintainer can push to any playground branch of
>> other packages), then post the links to the commit(s), and the CI log?
-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry


More information about the Cygwin-apps mailing list