From 0945fd7cab8d9b098f37c43eb45f3f6be6d1deac Mon Sep 17 00:00:00 2001 From: Page Asgardius Date: Sat, 28 Dec 2024 12:24:15 -0700 Subject: [PATCH] new ebuilds --- .../virtualx-engine-3.6.ebuild | 4 +- games-puzzle/r3-game/r3-game-0.2.1.ebuild | 2 +- net-p2p/chia-cli-bin/Manifest | 2 + .../chia-cli-bin/chia-cli-bin-2.5.0.ebuild | 172 ++++++++++++++++++ net-p2p/chia-gui-bin/Manifest | 2 + .../chia-gui-bin/chia-gui-bin-2.5.0.ebuild | 172 ++++++++++++++++++ 6 files changed, 351 insertions(+), 3 deletions(-) create mode 100644 net-p2p/chia-cli-bin/Manifest create mode 100644 net-p2p/chia-cli-bin/chia-cli-bin-2.5.0.ebuild create mode 100644 net-p2p/chia-gui-bin/Manifest create mode 100644 net-p2p/chia-gui-bin/chia-gui-bin-2.5.0.ebuild diff --git a/games-engines/virtualx-engine/virtualx-engine-3.6.ebuild b/games-engines/virtualx-engine/virtualx-engine-3.6.ebuild index 60b61b0..96d08fd 100644 --- a/games-engines/virtualx-engine/virtualx-engine-3.6.ebuild +++ b/games-engines/virtualx-engine/virtualx-engine-3.6.ebuild @@ -22,10 +22,10 @@ EAPI=8 # Take a look at the eclass/ directory for more examples. # Short one-line description of this package. -DESCRIPTION="puzzle game set in the asteroid belt (made with godot)" +DESCRIPTION="Game Engine Forked From Godot 3.6" # Homepage, not used by Portage directly but handy for developer reference -HOMEPAGE="https://git.asgardius.company/asgardius/midori-school" +HOMEPAGE="https://git.asgardius.company/asgardius/virtualx-engine" # Point to any required sources; these will be automatically downloaded by # Portage. diff --git a/games-puzzle/r3-game/r3-game-0.2.1.ebuild b/games-puzzle/r3-game/r3-game-0.2.1.ebuild index f5fa2e6..50f5bd5 100644 --- a/games-puzzle/r3-game/r3-game-0.2.1.ebuild +++ b/games-puzzle/r3-game/r3-game-0.2.1.ebuild @@ -25,7 +25,7 @@ EAPI=8 DESCRIPTION="puzzle game set in the asteroid belt (made with godot)" # Homepage, not used by Portage directly but handy for developer reference -HOMEPAGE="https://git.asgardius.company/asgardius/midori-school" +HOMEPAGE="https://git.asgardius.company/asgardius/r3-next" # Point to any required sources; these will be automatically downloaded by # Portage. diff --git a/net-p2p/chia-cli-bin/Manifest b/net-p2p/chia-cli-bin/Manifest new file mode 100644 index 0000000..aed81ee --- /dev/null +++ b/net-p2p/chia-cli-bin/Manifest @@ -0,0 +1,2 @@ +DIST chia-blockchain-cli_2.5.0-1_amd64.deb 224829628 BLAKE2B 33a19ffafa4f90205892892c250433ebabea3ed29f522b07206fb0cf1ade4d332f442d26b336b3a6d1df4b901147bb9002edbc40fe7ee67c48105c370fa0de00 SHA512 950f698a69db2e54c0fccb1d98b070c587a35a5a27ccdda21e4831bc5fdccfed9e065c3b58555cbfdb324751012855f8acf0017ecbe8c613fb491a6a689330b9 +DIST chia-blockchain-cli_2.5.0-1_arm64.deb 222357656 BLAKE2B 3ab85aa00a04e0dfd0379537aaf28e13368c5a1fa465d7a4cb6133c320a7987d472c12a4234b32ce02b2efdc54a8b6958e7c8ef2c5ce648a438966430f35c93d SHA512 9f531856de096454c83486bce2095c70c5cf1291fa241f09b1db5b84df255aec2672b08f8f6bf08ef329a8c7f08a0892ea1b687585c7e604330bad3dbbd0158b diff --git a/net-p2p/chia-cli-bin/chia-cli-bin-2.5.0.ebuild b/net-p2p/chia-cli-bin/chia-cli-bin-2.5.0.ebuild new file mode 100644 index 0000000..35b21bc --- /dev/null +++ b/net-p2p/chia-cli-bin/chia-cli-bin-2.5.0.ebuild @@ -0,0 +1,172 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# NOTE: The comments in this file are for instruction and documentation. +# They're not meant to appear with your final, production ebuild. Please +# remember to remove them before submitting or committing your ebuild. That +# doesn't mean you can't add your own comments though. + +# The EAPI variable tells the ebuild format in use. +# It is suggested that you use the latest EAPI approved by the Council. +# The PMS contains specifications for all EAPIs. Eclasses will test for this +# variable if they need to use features that are not universal in all EAPIs. +# If an eclass doesn't support latest EAPI, use the previous EAPI instead. +EAPI=8 + +# inherit lists eclasses to inherit functions from. For example, an ebuild +# that needs the eautoreconf function from autotools.eclass won't work +# without the following line: +#inherit autotools +# +# Eclasses tend to list descriptions of how to use their functions properly. +# Take a look at the eclass/ directory for more examples. + +# Short one-line description of this package. +DESCRIPTION="A new blockchain and smart transaction platform that is easier to use, more efficient, and secure. CLI only" + +# Homepage, not used by Portage directly but handy for developer reference +HOMEPAGE="https://www.chia.net/" + +# Point to any required sources; these will be automatically downloaded by +# Portage. + +SRC_URI=" + amd64? ( https://repo.chia.net/debian/pool/main/c/chia-blockchain-cli/chia-blockchain-cli_${PV}-1_amd64.deb ) + arm64? ( https://repo.chia.net/debian/pool/main/c/chia-blockchain-cli/chia-blockchain-cli_${PV}-1_arm64.deb )" + +# Source directory; the dir where the sources can be found (automatically +# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} +# If you don't need to change it, leave the S= line out of the ebuild +# to keep it tidy. +S="${WORKDIR}" + +# License of the package. This must match the name of file(s) in the +# licenses/ directory. For complex license combination see the developer +# docs on gentoo.org for details. +LICENSE="Apache-2.0" + +# The SLOT variable is used to tell Portage if it's OK to keep multiple +# versions of the same package installed at the same time. For example, +# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible +# with 1.2.2), it would be optimal to instruct Portage to not remove +# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this, +# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2. +# emerge clean understands SLOTs, and will keep the most recent version +# of each SLOT and remove everything else. +# Note that normal applications should use SLOT="0" if possible, since +# there should only be exactly one version installed at a time. +# Do not use SLOT="", because the SLOT variable must not be empty. +SLOT="0" + +# Using KEYWORDS, we can record masking information *inside* an ebuild +# instead of relying on an external package.mask file. Right now, you +# should set the KEYWORDS variable for every ebuild so that it contains +# the names of all the architectures with which the ebuild works. +# All of the official architectures can be found in the arch.list file +# which is in the profiles/ directory. Usually you should just set this +# to "~amd64". The ~ in front of the architecture indicates that the +# package is new and should be considered unstable until testing proves +# its stability. So, if you've confirmed that your ebuild works on +# amd64 and ppc, you'd specify: +# KEYWORDS="~amd64 ~ppc" +# Once packages go stable, the ~ prefix is removed. +# For binary packages, use -* and then list the archs the bin package +# exists for. If the package was for an x86 binary package, then +# KEYWORDS would be set like this: KEYWORDS="-* x86" +# Do not use KEYWORDS="*"; this is not valid in an ebuild context. +KEYWORDS="~amd64 ~arm64" + +# Comprehensive list of any and all USE flags leveraged in the ebuild, +# with some exceptions, e.g., ARCH specific flags like "amd64" or "ppc". +# Not needed if the ebuild doesn't use any USE flags. +IUSE="systemd upnp" + +# A space delimited list of portage features to restrict. man 5 ebuild +# for details. Usually not needed. +#RESTRICT="strip" + +# Run-time dependencies. Must be defined to whatever this depends on to run. +# Example: +# ssl? ( >=dev-libs/openssl-1.0.2q:0= ) +# >=dev-lang/perl-5.24.3-r1 +# It is advisable to use the >= syntax show above, to reflect what you +# had installed on your system when you tested the package. Then +# other users hopefully won't be caught without the right version of +# a dependency. +RDEPEND="dev-lang/python" + +# Build-time dependencies that need to be binary compatible with the system +# being built (CHOST). These include libraries that we link against. +# The below is valid if the same run-time depends are required to compile. +#DEPEND="${RDEPEND}" + +# Build-time dependencies that are executed during the emerge process, and +# only need to be present in the native build system (CBUILD). Example: +#BDEPEND="" + +# The following src_configure function is implemented as default by portage, so +# you only need to call it if you need a different behaviour. +#src_configure() { + # Most open-source packages use GNU autoconf for configuration. + # The default, quickest (and preferred) way of running configure is: + #econf + # + # You could use something similar to the following lines to + # configure your package before compilation. The "|| die" portion + # at the end will stop the build process if the command fails. + # You should use this at the end of critical commands in the build + # process. (Hint: Most commands are critical, that is, the build + # process should abort if they aren't successful.) + #./configure \ + # --host=${CHOST} \ + # --prefix=/usr \ + # --infodir=/usr/share/info \ + # --mandir=/usr/share/man || die + # Note the use of --infodir and --mandir, above. This is to make + # this package FHS 2.2-compliant. For more information, see + # https://wiki.linuxfoundation.org/lsb/fhs +#} + +# The following src_compile function is implemented as default by portage, so +# you only need to call it, if you need different behaviour. +#src_compile() { + # emake is a script that calls the standard GNU make with parallel + # building options for speedier builds (especially on SMP systems). + # Try emake first. It might not work for some packages, because + # some makefiles have bugs related to parallelism, in these cases, + # use emake -j1 to limit make to a single process. The -j1 is a + # visual clue to others that the makefiles have bugs that have been + # worked around. + + #emake +#} + +# The following src_install function is implemented as default by portage, so +# you only need to call it, if you need different behaviour. +src_install() { + tar -xf data.tar.xz -C "${D}" + + # You must *personally verify* that this trick doesn't install + # anything outside of DESTDIR; do this by reading and + # understanding the install part of the Makefiles. + # This is the preferred way to install. + #emake DESTDIR="${D}" install + + # When you hit a failure with emake, do not just use make. It is + # better to fix the Makefiles to allow proper parallelization. + # If you fail with that, use "emake -j1", it's still better than make. + + # For Makefiles that don't make proper use of DESTDIR, setting + # prefix is often an alternative. However if you do this, then + # you also need to specify mandir and infodir, since they were + # passed to ./configure as absolute paths (overriding the prefix + # setting). + #emake \ + # prefix="${D}"/usr \ + # mandir="${D}"/usr/share/man \ + # infodir="${D}"/usr/share/info \ + # libdir="${D}"/usr/$(get_libdir) \ + # install + # Again, verify the Makefiles! We don't want anything falling + # outside of ${D}. +} diff --git a/net-p2p/chia-gui-bin/Manifest b/net-p2p/chia-gui-bin/Manifest new file mode 100644 index 0000000..80293e3 --- /dev/null +++ b/net-p2p/chia-gui-bin/Manifest @@ -0,0 +1,2 @@ +DIST chia-blockchain_2.5.0_amd64.deb 171799974 BLAKE2B 5cd5e83d7f8654ca6696fa02743ff5699b4dcdfa2bd3c88b462d3c8cb5f9f7ef6396d352d7cb3ba9dc44f0cb21a93f58dcf62b7da820bcfd7fa6ca6d59fa7535 SHA512 fe0d5dc68be12e783d6b3e979ed5a82448679eb9cb21b034b1618c00e50eda6624d6bb14b8a0bad4081a56d584edbb7610e9babe61b2eff8e2aeeb9e5d390f64 +DIST chia-blockchain_2.5.0_arm64.deb 316249956 BLAKE2B 4e587cbc8b091690e4648afd01e1b1a762c65e0e372ecc5d91363fa16d60dd8fbffcaa1096ef11693f623e031ae80fbcdfca637e825f095863b56ec792d20bcb SHA512 ae338f02a8b9e1b3b6e03ceb82e96a266d20122ef1119f572664e673d31ce32a128493475552d70d93f2caf0aff77264937c0c13bafe773d74bf11d4004ae42a diff --git a/net-p2p/chia-gui-bin/chia-gui-bin-2.5.0.ebuild b/net-p2p/chia-gui-bin/chia-gui-bin-2.5.0.ebuild new file mode 100644 index 0000000..a1a96eb --- /dev/null +++ b/net-p2p/chia-gui-bin/chia-gui-bin-2.5.0.ebuild @@ -0,0 +1,172 @@ +# Copyright 1999-2024 Gentoo Authors +# Distributed under the terms of the GNU General Public License v2 + +# NOTE: The comments in this file are for instruction and documentation. +# They're not meant to appear with your final, production ebuild. Please +# remember to remove them before submitting or committing your ebuild. That +# doesn't mean you can't add your own comments though. + +# The EAPI variable tells the ebuild format in use. +# It is suggested that you use the latest EAPI approved by the Council. +# The PMS contains specifications for all EAPIs. Eclasses will test for this +# variable if they need to use features that are not universal in all EAPIs. +# If an eclass doesn't support latest EAPI, use the previous EAPI instead. +EAPI=8 + +# inherit lists eclasses to inherit functions from. For example, an ebuild +# that needs the eautoreconf function from autotools.eclass won't work +# without the following line: +#inherit autotools +# +# Eclasses tend to list descriptions of how to use their functions properly. +# Take a look at the eclass/ directory for more examples. + +# Short one-line description of this package. +DESCRIPTION="A new blockchain and smart transaction platform that is easier to use, more efficient, and secure" + +# Homepage, not used by Portage directly but handy for developer reference +HOMEPAGE="https://www.chia.net/" + +# Point to any required sources; these will be automatically downloaded by +# Portage. + +SRC_URI=" + amd64? ( https://github.com/Chia-Network/chia-blockchain/releases/download/${PV}/chia-blockchain_${PV}_amd64.deb ) + arm64? ( https://github.com/Chia-Network/chia-blockchain/releases/download/${PV}/chia-blockchain_${PV}_arm64.deb )" + +# Source directory; the dir where the sources can be found (automatically +# unpacked) inside ${WORKDIR}. The default value for S is ${WORKDIR}/${P} +# If you don't need to change it, leave the S= line out of the ebuild +# to keep it tidy. +S="${WORKDIR}" + +# License of the package. This must match the name of file(s) in the +# licenses/ directory. For complex license combination see the developer +# docs on gentoo.org for details. +LICENSE="Apache-2.0" + +# The SLOT variable is used to tell Portage if it's OK to keep multiple +# versions of the same package installed at the same time. For example, +# if we have a libfoo-1.2.2 and libfoo-1.3.2 (which is not compatible +# with 1.2.2), it would be optimal to instruct Portage to not remove +# libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this, +# we specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2. +# emerge clean understands SLOTs, and will keep the most recent version +# of each SLOT and remove everything else. +# Note that normal applications should use SLOT="0" if possible, since +# there should only be exactly one version installed at a time. +# Do not use SLOT="", because the SLOT variable must not be empty. +SLOT="0" + +# Using KEYWORDS, we can record masking information *inside* an ebuild +# instead of relying on an external package.mask file. Right now, you +# should set the KEYWORDS variable for every ebuild so that it contains +# the names of all the architectures with which the ebuild works. +# All of the official architectures can be found in the arch.list file +# which is in the profiles/ directory. Usually you should just set this +# to "~amd64". The ~ in front of the architecture indicates that the +# package is new and should be considered unstable until testing proves +# its stability. So, if you've confirmed that your ebuild works on +# amd64 and ppc, you'd specify: +# KEYWORDS="~amd64 ~ppc" +# Once packages go stable, the ~ prefix is removed. +# For binary packages, use -* and then list the archs the bin package +# exists for. If the package was for an x86 binary package, then +# KEYWORDS would be set like this: KEYWORDS="-* x86" +# Do not use KEYWORDS="*"; this is not valid in an ebuild context. +KEYWORDS="~amd64 ~arm64" + +# Comprehensive list of any and all USE flags leveraged in the ebuild, +# with some exceptions, e.g., ARCH specific flags like "amd64" or "ppc". +# Not needed if the ebuild doesn't use any USE flags. +IUSE="systemd upnp" + +# A space delimited list of portage features to restrict. man 5 ebuild +# for details. Usually not needed. +#RESTRICT="strip" + +# Run-time dependencies. Must be defined to whatever this depends on to run. +# Example: +# ssl? ( >=dev-libs/openssl-1.0.2q:0= ) +# >=dev-lang/perl-5.24.3-r1 +# It is advisable to use the >= syntax show above, to reflect what you +# had installed on your system when you tested the package. Then +# other users hopefully won't be caught without the right version of +# a dependency. +RDEPEND="dev-lang/python" + +# Build-time dependencies that need to be binary compatible with the system +# being built (CHOST). These include libraries that we link against. +# The below is valid if the same run-time depends are required to compile. +#DEPEND="${RDEPEND}" + +# Build-time dependencies that are executed during the emerge process, and +# only need to be present in the native build system (CBUILD). Example: +#BDEPEND="" + +# The following src_configure function is implemented as default by portage, so +# you only need to call it if you need a different behaviour. +#src_configure() { + # Most open-source packages use GNU autoconf for configuration. + # The default, quickest (and preferred) way of running configure is: + #econf + # + # You could use something similar to the following lines to + # configure your package before compilation. The "|| die" portion + # at the end will stop the build process if the command fails. + # You should use this at the end of critical commands in the build + # process. (Hint: Most commands are critical, that is, the build + # process should abort if they aren't successful.) + #./configure \ + # --host=${CHOST} \ + # --prefix=/usr \ + # --infodir=/usr/share/info \ + # --mandir=/usr/share/man || die + # Note the use of --infodir and --mandir, above. This is to make + # this package FHS 2.2-compliant. For more information, see + # https://wiki.linuxfoundation.org/lsb/fhs +#} + +# The following src_compile function is implemented as default by portage, so +# you only need to call it, if you need different behaviour. +#src_compile() { + # emake is a script that calls the standard GNU make with parallel + # building options for speedier builds (especially on SMP systems). + # Try emake first. It might not work for some packages, because + # some makefiles have bugs related to parallelism, in these cases, + # use emake -j1 to limit make to a single process. The -j1 is a + # visual clue to others that the makefiles have bugs that have been + # worked around. + + #emake +#} + +# The following src_install function is implemented as default by portage, so +# you only need to call it, if you need different behaviour. +src_install() { + tar -xf data.tar.xz -C "${D}" + + # You must *personally verify* that this trick doesn't install + # anything outside of DESTDIR; do this by reading and + # understanding the install part of the Makefiles. + # This is the preferred way to install. + #emake DESTDIR="${D}" install + + # When you hit a failure with emake, do not just use make. It is + # better to fix the Makefiles to allow proper parallelization. + # If you fail with that, use "emake -j1", it's still better than make. + + # For Makefiles that don't make proper use of DESTDIR, setting + # prefix is often an alternative. However if you do this, then + # you also need to specify mandir and infodir, since they were + # passed to ./configure as absolute paths (overriding the prefix + # setting). + #emake \ + # prefix="${D}"/usr \ + # mandir="${D}"/usr/share/man \ + # infodir="${D}"/usr/share/info \ + # libdir="${D}"/usr/$(get_libdir) \ + # install + # Again, verify the Makefiles! We don't want anything falling + # outside of ${D}. +}