It makes sense to keep this here after ~arm64 is added, but
keywordreqs with -* are messy so remove it for now.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
It makes sense to keep this here after ~arm64 is added, but
keywordreqs with -* are messy so remove it for now.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Haven't had a proper look at this package (dead upstream),
but wouldn't hurt to tidy ebuild a bit still.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Will make the ~arm64 keywordreq easier and, while it does not
make sense to keyword on arches without wine, there's technically
no limitation that stops this here.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Not adding wine-proton given really no intention to keyword that one
on arm64, rather unlikely Valve tests it there and they will not offer
support if something is broken.
Note USE=mono is use.mask'ed on arm64 either way, but explicitly list
it given it's not about the same packages for wine. In the future may
instead need to unmask it here to allow a future ported wine-mono.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Not needed for ebuilds using the new wine.eclass, albeit
older un-migrated ebuilds due for eventual cleanup are
still broken. Would rather avoid leaving complex range
masks over these.
+mingw remains a default, so it shouldn't affect most
even if using old ebuilds.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Only the latest, wine-staging ebuilds are not meant for archiving
(use vanilla) and will likely delete sooner than later.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Trying to keep Wine ebuilds in sync between wine-vanilla, wine-staging,
and wine-proton which each have several ebuilds been giving headaches,
and the addition of arm64 support is not helping.
Goal is to offload only the gritty toolchain and slotting bits, and
leave ebuilds to deal with normal dependencies and configure options.
Could've put these in the eclass too, but it'd likely become messy as
dependencies get added/removed between versions (want to avoid too many
${PV} -gt rules). Also want to avoid these to allow overlays to use
this to package their own variants with more freedom.
Note there is some difference compared to current ebuilds:
- arm64 support using https://github.com/gentoo/gentoo/pull/41650
as a guideline (not tested myself, pending keywording)
- no support for non-PE builds to simplify and having less to
test, wine-proton was already doing this to match what upstream
Proton does
- ^ may be a bit misleading but if USE=-mingw, will still do PE
builds but using clang (less tested, so +mingw remains default),
debated USE=clang and dropping USE=mingw instead but that feels
confusing for other reasons
- drop REQUIRED_USE that prevented USE="wow64 -mingw"
- drop workaround that ensured man pages were installed for
a pure (non-default) 64bit build (feels not worth it, and
no longer needed for >=10.2)
- no support for <wine-9 (pre --enable-archs), will likely
drop these once they start causing problems and not worth
extra eclass logic
- bit of refactoring that could well be broken
In the future may have the eclass handle extra things like basic tests
too (full testsuite is nightmare), but leaving that out for now.
Closes: https://github.com/gentoo/gentoo/pull/41650
Closes: https://github.com/gentoo/gentoo/pull/41660
Thanks-to: Sasha Finkelstein <fnkl.kernel@gmail.com>
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Hans de Graaff
Sam James
Michał Górny
Ionen Wolkens