Subslot operator dep is rather iffy here, so ensure enchant:2
gets used in a revbump - now that we can
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
Our logrotate file was being installed with doins, leaving it with a
".logrotate" suffix on the live filesystem. This was harmless, but
looks a bit weird. Now it's installed as "/etc/logrotate.d/${PN}".
Closes: https://bugs.gentoo.org/707952
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Michael Orlitzky <mjo@gentoo.org>
The patching was done bad, calling default instead of gnome2_src_prepare;
use GNOME2_EAUTORECONF="yes" instead to work in correct order as well.
Also remove the now unnecessary -r1 p.mask (-r2 is not masked on purpose,
as it's now ready to enter ~arch as enchant:2 is not p.masked)
Closes: https://bugs.gentoo.org/660720
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
* Make parallel-installable with enchant-1.6
* Drop unnecessary static-libs support
* Port to EAPI-7
* Fix LICENSE
* Drop unnecessary USE=test, which is commented out and restricted
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
It looks like both enchant-2.pc and enchant.pc are checked, but
the cmake is making my head spin.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
It checks only for enchant.pc, but not the parallel-installable
enchant-2 versions (just the early ones that had enchant.pc still,
but changed ABI). Appears to be the case in current 9999 clone
as well.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
1.30 appears to only work with enchant:0 (1.6 and the early enchant-2
versions that didn't parallel-install), while the newers ones can work
with either at configure time. So lock to enchant:0 for 1.30 and change
to enchant:= for the rest for the time being.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
Only libenchant.so* is tried to be dynamically opened at runtime,
not libenchant-2.so, therefore having only enchant:2 would break
pyenchant and we need to pull in older SLOT of it.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
>=enchant-2 in unmasked form will be in a SLOT=2, thus we can restore
the minimum enchant requirement while specifying enchant:0 as the dep.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
It's not ideal to := depend, but configure checks for enchant-2 first,
so a locking to enchant:0 would be wrong as well. So use a subslot
operator for now, and this should be revbumped later to lock to
enchant:2 instead.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
Only libenchant.so is tried to be dynamically opened at runtime,
not libenchant-2.so; hexchat-2.14 versions try them all (and the
runtime dep appears removed).
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
configure checks only for enchant.pc, not enchant-2.pc
The still p.masked 3.0.10 uses enchant-2 only instead.
Package-Manager: Portage-2.3.84, Repoman-2.3.20
Signed-off-by: Mart Raudsepp <leio@gentoo.org>