On Fri, 25 Apr 2025, Jeremy Drake via Cygwin-apps wrote: > On Fri, 25 Apr 2025, Jeremy Drake via Cygwin-apps wrote: > > > Nah, not hard or complicated, I already went through the process locally. > > I just need to memorialize it in the cyport (and look at my setup log to > > see the handful of sphinx packages I installed, off the top of my head > > sphinx-build, applehelp, devhelp, qthelp, alabaster). Then the > > configury needed a patch because newer sphinx-build doesn't report its > > version in --help, but rather in --version. > > Updated to build html docs. Used URLs to Gentoo patches. Used same name > for split package as Debian (udcli instead of udis86 - I don't figure the > cli to be all that useful compared to the library, there are already > plenty of fine disassembler tools). > > Do I need to override categories for the cli/devel/docs packages? > > Hopefully I'll get a git repository soon to keep track of this. I don't > really consider emailing attachments all that sustainable. I've created a > gist now at > https://gist.github.com/jeremyd2019/2af8697a6978f8c580f7e8956f049437
I put together a github actions workflow to build the cygport from the gist, based on scallywag. Artifacts on https://github.com/jeremyd2019/udis86-cygport-build/actions/runs/14678025959
