Re: [ITA] Patch: update to source-highlight-3.1.9-1 (remove dep. to boost-1.66)

Jon Turney via Cygwin-apps <[email protected]> Fri, 6 Mar 2026 15:27:10 +0000
Newsgroups gmane.os.cygwin.applications
Message-ID <[email protected]>
On 23/01/2026 10:16, Carlo B. via Cygwin-apps wrote:
> Hello,
> with reference to the recent release of the test version of Boost C++
> 1.90.0 libraries,
> 
> https://cygwin.com/pipermail/cygwin-announce/2026-January/012793.html
> 
> it may happen that you won't be able to remove previous version
> because some packages depend on them. So, it happened to me that I was
> not able to uninstall completely the older version 1.66 because
> source-highlight package needs it.
> I don't remember why I had to install it, however I took the chance to
> update current version from 3.1.8 to 3.1.9, rather than simply
> rebuilding.
> You can find it here:
> 
> https://github.com/carlo-bramini/packages-cygwin/tree/main/source-highlight/source-highlight.x86_64
> 
> The rewritten script for cygport also adds missing information like
> license and dependencies.
> If you are planning to abandon the older versions of Boost C++ in
> favour of the new one, this update may be used for removing this
> dependency.

Yes, rebuilding stuff which depends on the older boost library so we can 
remove it is definitely something that needs doing.

> I hope that you will find it useful.

Thanks.

Despite the subject, this isn't actually a patch.  A 'git format-patch' 
against [1] would be much easier to work with, (rather than having to 
download your source archive to unpack it to get at the updated cygport...).

I'm slightly surprised this actually builds for you: the ./configure 
script tries to locate a library to link again for boost::regex, but 
that is header-only in boost 1.90, so I needed an extra patch for that.

>  libsource_highlight4_CONTENTS="
>        usr/bin/cygsource-highlight*.dll"

Generally, it's a really bad idea to write something like this.  If the 
soversion changes from 4 to 5, you probably won't notice. Then we'll 
have a libsource-highlight4 package containing 
cygsource-highlight-5.dll, which will break everything that depends on 
that package and expects it to provide a cygsource-highlight-4.dll.

(Ideally, we'd probably have some automated check in cygport for this 
kind of mix up, but someone has yet to write it...)

Anyhow, I used this as a basis for an updated source-highlight package.


Thanks again!

[1] https://cygwin.com/cgit/cygwin-packages/source-highlight/