On Fri, 25 Apr 2025, Brian Inglis via Cygwin-apps wrote:

> Later (2014-12-25!) developer sources:
>
>       https://github.com/vmt/udis86
>
> updated fork sources additions and fixes from multiple acked upstreams:
>
>       https://github.com/canihavesomecoffee/udis86
>
> used by Debian packager:
>
>       https://salsa.debian.org/NyxTrail/udis86
>
> see files under debian/; released as +20221013 - we would use 1.7.2+20221013.

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, and it seemed from the repology link that most others do the
same.  They also inherit from a python eclass and pass ${PYTHON} to
configure.  I had that in a prior revision that I didn't send, before I
switched to BUILD_REQUIRES="python3" - I think I prefer that and will
switch back.

> Cygport assumes and performs "inherit autotools" - sometimes produces
> mysterious messages!
>
> >> I suggest to put patches from Gentoo in a subdir "gentoo", and
> >> similarly for any existing outside patch, so that in the future we know
> >> where this is from (lots of mystery patches in repos), and so one can
> >> potentially look again if something changed where it comes from.
> >
> > New version of the cygport attached (the patches didn't change so I'm not
> > re-attaching them).
>
> I've always used remote URI definitions for upstream patches, for example:
>
> # patch source repos - note *plain* text format patches
> DEBIAN=https://sources.debian.org/data/main/${NAME:0:1}/$NAME/1.7.2-1/debian/patches
> # Fedora patches from explicit latest f4# branch rather than rawhide or main!
> FEDORA=https://src.fedoraproject.org/rpms/$NAME/raw/f42/f # explicit f42
> branch
> GENTOO=https://gitweb.gentoo.org/repo/gentoo.git/plain/dev-libs/$NAME/files
> OPENSUSE=https://raw.githubusercontent.com/bmwiedemann/openSUSE/raw/refs/heads/master/packages/${NAME:0:1}/$NAME
> PATCH_URI="
>       $DEBIAN/...patch
>       $FEDORA/...patch
>       $GENTOO/$NAME-1.7.2-docdir.patch
>       $GENTOO/$NAME-1.7.2-python3.patch
>       $GENTOO/$NAME-1.7.2-uninitialized-variable.patch
>       $OPENSUSE/...patch
> "     # keep explicit upstream versions for use with future versions

That makes sense.

They also have the ability to make html docs, but they are not part of the
normal build/install, and they require a bunch of sphinx packages.
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?

Reply via email to