A full check-upgrade-status sweep of meta-oe found 121 recipes reporting
UNKNOWN_BROKEN: their upstream version check resolved no version. This
adds the correct check metadata to each so the version check works again.
Fixes, by mechanism:
- wget/tarball recipes: add UPSTREAM_CHECK_URI + UPSTREAM_CHECK_REGEX
pointing at the real release listing (SourceForge files pages, GitHub
releases pages, GNU/ftp mirrors, distro pools).
- git recipes with release tags in a non-default format: add
UPSTREAM_CHECK_GITTAGREGEX matching the actual tag scheme.
- git repos with no tags at all: UPSTREAM_CHECK_COMMITS = "1".
- recipes whose upstream has no checkable release channel, or whose PV
format cannot be compared against upstream tags (CPAN zero-padded
versions, AUTOINC "git" PVs, dash-separated tags the checker cannot
convert): UPSTREAM_VERSION_UNKNOWN = "1" with an explanatory comment.
Also override GITHUB_BASE_URI for libppd's sibling libcupsfilters where the
github-releases class default pointed at a non-existent org (404).
Only version-check metadata is touched; no SRC_URI, SRCREV, PV, or checksum
is changed, so nothing that gets built is affected. Each fix was verified
with devtool check-upgrade-status: 120 of 121 now resolve (MATCH, UPDATE,
COMMITS, or an honestly-declared UNKNOWN). The remaining recipe (libubox)
already has correct metadata and only fails locally because the git://
port to git.openwrt.org is firewalled on the build host.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Replace the long-dead anthy 9100h (last released 2009, fetched from an old
Ubuntu source tarball) with the maintained fork anthy-unicode, which is UTF-8
native and actively released on GitHub.
anthy-unicode renames its libraries (libanthy-unicode, libanthydic-unicode,
libanthyinput-unicode), pkg-config module file (anthy-unicode.pc), headers
(includedir/anthy-unicode-1.0/anthy), config file (anthy-unicode.conf) and
binaries (anthy-*-unicode). The recipe and packaging are updated accordingly:
libanthy-unicode0 for the runtime libraries and the standard PN-dev for the
development files.
The cross-compilation strategy is carried over from the old recipe: dictionary
generation runs helper programs (mkfiledic, mkworddic, mkdepgraph, calctrans,
proccorpus) that cannot execute when cross compiling. native-helpers.patch
promotes them to bin_PROGRAMS so anthy-unicode-native stages them into the
native sysroot; target-helpers.patch makes the target dictionary rules call
them from PATH instead of ./. not_build_elc.patch avoids byte-compiling the
Emacs lisp (no target Emacs under cross compilation). The patches are
regenerated against anthy-unicode's -unicode-suffixed libtool archives. The
legacy 2ch_t.patch is dropped; anthy-unicode has no mkanthydic/2ch.t.
uim is switched from the legacy EUC-JP anthy backend to the UTF-8
anthy-unicode backend it already supports: configure with --without-anthy
--with-anthy-utf8, DEPENDS on anthy-unicode, and the uim-anthy package is
renamed uim-anthy-utf8 (plugin libuim-anthy-utf8, anthy-utf8*.scm, module
registered as anthy-utf8) with RDEPENDS on libanthy-unicode0.
packagegroup-meta-oe: anthy -> anthy-unicode.
Verified by building anthy-unicode-native and anthy-unicode for
x86-64 (do_package_qa clean): the native helpers stage into the native
sysroot, the target build generates anthy.wdic/anthy.dep/anthy.dic via those
native helpers, and packaging splits into anthy-unicode, libanthy-unicode0 and
anthy-unicode-dev. uim variables verified by parse (it requires the x11
DISTRO_FEATURE, which the qemux86-64 yoe distro strips, so it is not buildable
in this configuration).
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Khem Raj