On 2025-04-25 16:42, 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
Once your SSH key is accepted and associated with your package(s) in
https://cygwin.com/git/cygwin-infra/pkg-maint.
you should have a git repo init'ed for your cygport and patches, and do a lazy
remote repo creation by pushing to its upstream:
$ git config remote.origin.url ssh://cyg...@cygwin.com/git/cygwin-packages/$PKG
$ git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
$ git config branch.master.remote origin
$ git config branch.master.merge refs/heads/master
$ git config branch.playground.remote origin
$ git config branch.playground.merge refs/heads/playground
[I assume but do not know if you may also be able to use branch main?]
--
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
