Arch Linux User Repository

... There are already better tools out there

Could you specify what you mean ?

Do you mean there is a better tool that does for gemini what curl dose for http ?

Or do you mean better "general" gemini tools ?

I'm not asking about gemini tools in general. I am quite familiar and tested almost all of them. Personally for (TUI) gemini browsing I use telesecope.

What I am looking for is a simple curl like tool for gemini that i can trust for usage in (shell) scripts.

Another usage for such curl alike tool is in for example, https://git.sr.ht/~k1nkreet/gemivim. It's a superb vim plugin that allows you to "stay in vim" while browsing gemini. It currently depends on "gmni".

Trust means, gets maintained, is small, no bloat, is in official repos etc...

• gmni
• gemget, old, go, seems abandoned, https://github.com/makew0rld/gemget

I could, but I dont want to be using "openssl" or "netcat" hacks in shell scripts to make gemini requests.

Could this same "cgmnlm" be its replacement as an official Arch package?

I don't think so.

Is there a real commitment of caring about this fork for the future?

For the time being i will take care that it at least works, but there will most probably no fundamental changes anymore. There are already better tools out there.

@Rene

Thanks for maintaining the PKGBUILD and the tool itself. Just a question and some thoughts and observations.

I would also like to know your personal thoughts/opinions on this.

I am curious about the "future" of the original "gmni" and this same fork. Could this same "cgmnlm" be its replacement as an official Arch package ? Maybe one could ask the Arch packager about this ? Is there a real commitment of caring about this fork for the future ?

Here is something I noticed,

Currently the "official|" Archlinux "gmni",

Repository      : extra
Name            : gmni
Version         : 1.0-2
Description     : A Gemini client
URL             : https://git.sr.ht/~sircmpwn/gmni
Depends On      : bearssl
Optional Deps   : None
Conflicts With  : None
Replaces        : None
Packager        : George Rawlinson <grawlinson@archlinux.org>
Build Date      : Mon 29 May 2023 11:02:02 PM WEST

So that's it. It was built for Arch almost 2 years ago. No change since then.

Let's have look at its source repo, https://git.sr.ht/~sircmpwn/gmni

12de5cf 3M Drew DeVault        o [master] {origin/master} {origin/HEAD} R
2f976c5 2Y Drew DeVault        o README.md: add maintenance notice
74c0861 2Y Ondřej Fiala        o gmnlm: treat invalid cert and cert misma
e4d3984 2Y Ondřej Fiala        o gmnlm: make ./ prefix mandatory for rela

So, he basicly hasnt done anything in the last 2 years.

In January 2023, he adds this,

commit 2f976c52dcfaaaa5b83a9208f07b04343d38f594
Author:     Drew DeVault <sir@cmpwn.com>
AuthorDate: Mon Jan 16 13:33:23 2023 +0100

    README.md: add maintenance notice

+**Notice**: This project is no longer maintained.

And almost 2 years later in December 2024 he changes to,

commit 12de5cfa2310284a617d3ef09a8c2fd6acae6139
Author:     Drew DeVault <sir@cmpwn.com>
AuthorDate: Mon Dec 9 15:55:49 2024 +0100

    README: s/no longer maintained/complete/

-**Notice**: This project is no longer maintained.
+**Notice**: This project is complete.

Hhmmmm ... Would have been nice if he had pointed to the cgmnln fork or others.

Rumours have it, he, Drew, had a lot of interest in Gemini some time ago, https://drewdevault.com/2020/11/01/What-is-Gemini-anyway.html

November 1, 2020 What is this Gemini thing anyway, and why am I excited about it?

Some time later, alas, the prophet changes his mind and disappears. He even removed his gemini capsule.

But, there are still those of us interested and commited to gemini use with proper maintained tools. And who dont follow things just because they are hype.

So conclusion.

Because I usually prefer to avoid AUR tools as much as possible. I would like to make sure my gemini tools are official packages. They are at least healthy, monitored and screened for critical security bugs. And its dependencies, ssl thingys, etc.

That is what I basicly want for a fundamental tool like "gmni" that is like a "curl" a critical piece of infrastructure.

It's not like I have any request for new features at all. Nor I expect to see frenetic activity on a git repo to make sure it is alive. I just want to make sure it is not abandoned and left unmonitored.

It is a written in 'C' tool. It should be robust and future prone I guess. But one never knows.