On 2025-04-25 14:26, Jeremy Drake via Cygwin-apps wrote:
On Fri, 25 Apr 2025, Philippe Baril Lecavalier via Cygwin-apps wrote:
On 2025-04-25 3:28 p.m., Jeremy Drake via Cygwin-apps wrote:
Do you think I should follow Debian here and use that fork? Do I have to
source the package from git then? Gentoo still follows the actual last
release
Each used their own expert judgement, as you shall! I'm a bit surprised that
Gentoo went with actual release while Debian went with something seemingly
less vanilla. They may have their reasons.
My first reflex would be to go with the last "release". If that doesn't work
or there are problems (won't build, expects jurassic dependencies, etc.), we
learn something. Even if this compiles, there might be some longstanding bug
that those forks ironed out of this abandonware. Then try those until you get
something that is functional to your satisfaction.
The only "jurassic dependency" is that the scripts were still python2.
The patch from Gentoo to update them to python3 was quite small though.
Doesn't look like gentoo bothers with them but Debian does. Should I try
to build+package them, or just let people go to udis86.readthedocs.io?
Try? Yes!
If you run into some really complicated bug that prevents building
documentation (crashes, hangs, impossible to meet dependency), it's ok to give
up or sacrifice some part of it (do raise the issue somewhere), better to have
working software and no docs than the opposite. The fact that there is a long
list of stuff involved to produce it is a burden only for the package
maintainer (embrace it, you shall), not the user, and only once in a while.
You are not expected to rebuild and repost the package every five minutes.
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.
When you have a new package or issues with features of builds, those URIs I
quoted above are also useful to download the RPM specs, EBUILDs, PKGBUILDs,
debian/dsc control rules, etc. to see what other distros do and how they do it.
For example, I add PDF and HTML docs to SRC_URI+= where available, as from
gnu.org/s/$NAME/manual/$NAME.{{dvi,html,{html_node,info,texi}.tar,txt}.gz,pdf}
to add to DOCS or src_install(){...} under doc/$PKG/{,html}/.
--
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
