Also updated to EAPI=7 and dropped user eclass
in favour of acct-* packages.
Package-Manager: Portage-2.3.70, Repoman-2.3.16
Signed-off-by: Conrad Kostecki <conrad@kostecki.com>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
UID 490 will be used, as its available.
Arch and Fedora don't have a UID for the minecraft user.
Package-Manager: Portage-2.3.70, Repoman-2.3.16
Signed-off-by: Conrad Kostecki <conrad@kostecki.com>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
GID 490 will be used, as its the next available.
Arch and Fedora don't have a GID for the minecraft group.
Package-Manager: Portage-2.3.70, Repoman-2.3.16
Signed-off-by: Conrad Kostecki <conrad@kostecki.com>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
This ebuild uses EAPI 7 and introduces USE flags 'rspamd' and
'rspamd-https' to support Amavis' new Rspamd extension.
Package-Manager: Portage-2.3.69, Repoman-2.3.16
Signed-off-by: Ralph Seichter <gentoo@seichter.de>
Signed-off-by: Michael Orlitzky <mjo@gentoo.org>
Now I better understand what variables to use in which conditions,
I now see that this working at all was somewhat a miracle, given
ROOT is defined to not exist in src_configure, and EROOT is ...
"${ROOT}/${EPREFIX}"
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
Note: USE="java" is currently unsupportable, and will be shortly
followed with a package.use.mask entry, as it requires JDK9 to work,
and JDK9+ support is somewhat taking a pre-climate-change glacial
pace.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
Note that this ebuild currently is unusable as:
1. Using moar w/ moar-9999 currently has an odd problem where it needs
to use a non-existent "ffi.h"
2. Using jvm currently is unsupportable as upstream currently requires
jdk-1.9/9, which we presently don't have any support for in Gentoo.
Hopefully these issues won't be present when I use this ebuild as a
base for the most recently shipped nqp release.
See also: https://github.com/perl6/nqp/issues/571
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
Due to jdk/jre-1.7 being mentioned in (R)DEPEND, java-pkg_javac-args
injects "-source 1.7 -target 1.7" into the javac invocation, which is
silly, as nqp then appends "-source 1.8" to it anyway, resulting in:
javac -source 1.7 -target 1.7 -source 1.8 ....
And javac then barfs:
javac: source release 1.8 requires target release 1.8
Bumping the values in DEPENDS changes the javac invocation to:
javac -source 1.8 -target 1.8 -source 1.8 ...
Which of course then works.
Subsequently, all existing nqp versions (other than -9999) now work
for me with USE="java" just fine, where previously they wouldn't work
at all.
Closes: https://bugs.gentoo.org/631226
Closes: https://bugs.gentoo.org/626486
Closes: https://bugs.gentoo.org/635902
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
The existing SRC_URI's used githubs /tarball/ API, which is now
obsoleted by the /archive/ API.
Additionally, Upstream provide official release archives in
/releases/
Both of these endpoints obsolete the use of the vcs-snapshot eclass.
However, both of these endpoints return different archives, with
different checksums, so cache-avoidance must be done for the
checksums to give correct results for all users.
Package-Manager: Portage-2.3.66, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
Petr Vaněk
Manuel Rüger
Joonas Niilola
Scott Martin
Michał Górny
Conrad Kostecki
Mikle Kolyada
Guilherme Amadio
Ralph Seichter
Lars Wendler
Ben Kohler
Kent Fredric
Michael Palimaka