Arch Linux User Repository

@fiz I saw aur/gforth abandoned and took it over to get it working again. I see it's a 'depend' here, can you confirm this is intended? I can confirm it successfully compiles and replaces aur/gforth with this -git version.

I was going to modify aur/gforth to follow the tagged releases from git, but I'm not sure if that's the best approach.

My two questions:

-Should I leave aur/gforth at 0.7.3?

-Is aur/gforth a package you'd like to maintain?

fiz, that's totally okay and no worries at all. It's an overstatement I have any real contribution because it rarely needs my attention -- but thanks for saying that.

I've added you to the co-maintainer of the package and you should have full access to the aur git repo now. Then if you can confirm that I'll disown the package, which will automatically makes you the owner.

Ref: https://bbs.archlinux.org/viewtopic.php?id=270656

b4283, if you are okay with that sure, I can take it over. But I don't want to rip it away from you, since we appreciate your work over the last 5 years, we can also call a webhook of your choice to bump the version, if you want to do that.

Please let me know your choice, and if you want to hand the package over, please point me to the HowTo (could not find instructions for a direct handover, only orphaned and the like).

fiz, you can take over the package if that works better for you

hi, I am one of the Gforth maintainers and we were wondering if it would be possible to update the version of this package via CI, as we are doing for other distros. As we understand, all that would be required is checking out the package-repo, update the pkgver variable to the latest tag and commit&push it. Please let us know if we can add this to our CI, or if we can call a webhook somewhere to make this happen.

From 11c59f5fc9617afcacdba82dad12ab987fedb820 Mon Sep 17 00:00:00 2001
From: Kimapr <kimapr@mail.ru>
Date: Thu, 7 Dec 2023 11:29:23 +0500
Subject: [PATCH] Fix missing autoconf and automake dependency

---
 PKGBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 56b2fee..ec42ede 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,12 +1,12 @@
 pkgname=gforth-git
-pkgver=20181103
+pkgver=20231204
 pkgrel=1
 pkgdesc="Gforth is the Forth implementation of the GNU project."
 arch=(i686 x86_64)
 url="https://www.gnu.org/software/gforth"
 license=('GPLv3')
 depends=()
-makedepends=("make" "git" "gforth" "texinfo")
+makedepends=("make" "git" "gforth" "texinfo" "automake" "autoconf")
 provides=("gforth")
 conflicts=("gforth")
 source=('git+https://git.savannah.gnu.org/git/gforth.git')
-- 
2.43.0

please update version number, new gforth is 0.7.9_20230518

gforth also requires 'tex' binary to for make doc .. does that need to be a build dependency? Or am I missing a common dependency?

Also, a minor problem: Gforth now reports the original locations of redefined words, but the way it's built here causes it to report relative paths for its own libraries (usr should be /usr):

condit.fth:35:35: warning: redefined catch with CATCH
usr/share/gforth/0.7.9_20190214/kernel/basics.fs:240:7: warning: original location

Need to comment out the chcon call in configure.ac to make this build properly (I don’t use SELinux). No idea if this is a Gforth problem or an SELinux one, but this “fix” would probably break the build on an SELinux system.

diff -aur -x .git src.old/gforth/configure.ac src/gforth/configure.ac
--- src.old/gforth/configure.ac 2019-02-15 18:04:08.167472880 +0300
+++ src/gforth/configure.ac 2019-02-15 18:02:27.142686145 +0300
@@ -963,7 +963,7 @@

 #work around SELinux brain damage (from Andrew Haley <12t8f3jakb74g2c@news.supernews.com>)
 #This magic incantation  seems to be completely undocumented.
-AC_CHECK_PROG([MASSAGE_EXE],[chcon],[chcon -t unconfined_execmem_exec_t],[true])
+dnl AC_CHECK_PROG([MASSAGE_EXE],[chcon],[chcon -t unconfined_execmem_exec_t],[true])

 #Now a little support for DOS/DJGCC
 GFORTHFAST_EXE="$GFORTH_EXE"