Re: [PATCH cygutils 0/1] Notes

Mark Geisert via Cygwin-apps <[email protected]>
Newsgroups gmane.os.cygwin.applications
Message-ID <[email protected]>
Hi Brian, Vadim,

On Wed, 6 Aug 2025, Brian Inglis via Cygwin-apps wrote:
> On 2025-08-06 08:07, Vadim (vadcx) via Cygwin-apps wrote:
>> From: "Vadim (vadcx)" <[email protected]>
>> I couldn't figure out how to build cygutils and got confused along
>> the way, where the repository is supposed to be and how maintainer's
>> patches should be applied.
>
> Start with the package source summary page:
>
> 	https://cygwin.com/packages/summary/cygutils-src.html
>
> to get to the packaging repo:
>
> 	https://cygwin.com/cgit/cygwin-packages/cygutils/
>
> which you can clone from the https URI there;
> although there is still a historical cygwin-apps repo also:
>
> 	https://cygwin.com/cgit/cygwin-apps/cygutils/
>
> but chere has no source summary page, just package:
>
> 	https://cygwin.com/packages/summary/chere.html
>
> so the source package cygports there should be your start point, as there 
> does not appear to be any packaging repo pushed as yet.
>
> The apps repos maintainer (Jon or alternate) can create one with available 
> history.
>
> Patches must apply cleanly against the HEAD of main/master or equivalent.
>
> You may need to bump versions

Speaking from memory because I haven't checked yet, I believe the 
packaging repo still refers to Charles Wilson's last release.  I have not 
kept that repo (the one under Cygwin.com/cgit) in sync with the updates I 
have made in the years since.

Vadim, Brian's text above is how it's supposed to work, and how it works 
for most if not all other Cygwin packages.  I will be converging cygutils 
to this standard over time, but not soon.

Nevertheless, I have seen your patch posts and will respond to them 
shortly.  They will result in an updated cygutils package in due time.
Apologies for any confusion,

..mark
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.