Package Details: lagrange 1.19.3-1

Git Clone URL: https://aur.archlinux.org/lagrange.git (read-only, click to copy)
Package Base: lagrange
Description: Beautiful Gemini Client
Upstream URL: https://git.skyjake.fi/skyjake/lagrange
Licenses: BSD
Submitter: Roshless
Maintainer: Roshless
Last Packager: Roshless
Votes: 44
Popularity: 0.40
First Submitted: 2020-10-10 19:45 (UTC)
Last Updated: 2025-10-04 09:11 (UTC)

Pinned Comments

Roshless commented on 2020-11-04 08:20 (UTC) (edited on 2022-08-23 13:45 (UTC) by Roshless)

Instead of flagging this package out of date please send patches to repo using mailing list linked in index.md.

Tutorial: https://git-send-email.io/

Latest Comments

1 2 3 4 5 6 7 Next › Last »

shtrophic commented on 2025-09-08 18:16 (UTC)

Hi, for the webp and jxl decoders: can you enable them at compiletime? Archlinux policy says that software should be built with all its features by default: https://wiki.archlinux.org/title/PKGBUILD#depends

kallisti5 commented on 2025-08-07 14:01 (UTC)

why is this not in the Arch package repo yet? It's great.

dmerejkowsky commented on 2024-10-23 14:32 (UTC)

I think this happens because you interrupted a previous build and got a partial download.

Try running:

$ rm *.part

and try again

slondr commented on 2024-10-22 21:38 (UTC) (edited on 2024-10-22 21:39 (UTC) by slondr)

Seems to no longer build, I get the following error:

curl: (33) HTTP server does not seem to support byte ranges. Cannot resume.
==> ERROR: Failure while downloading https://git.skyjake.fi/skyjake/lagrange/releases/download/v1.18.3/lagrange-1.18.3.tar.gz

yochananmarqos commented on 2023-04-28 20:54 (UTC)

@Roshless: Since the maintainer likes to belittle anyone commenting here and project, I'll just post my improved PKGBUILD.

Roshless commented on 2023-01-25 21:31 (UTC)

@yochananmarqos people like you are the single biggest reason there is always maintainer shortage.

What account? Did you really bother to type all this text into aur before checking what mailing list really is? You only need mail account and git installed- that's the point, no need for account on gitlab/sourcehut

Flagging package out of date is not contribution, sending a patch with updated version is. Yes I have rss feeds, but there is this thing called real life that can take some time off my non-paid time keeping packages up to date.

I don't need your high horse spiel about out of date flag purpose and aur helpers- I know, Ive been around for ~10y on this site.

Instead of being all smart in your comment, maybe next time send a patch? If you know what you are doing, it takes comparable amount of time to flagging package out of date and copy pasting link to release.

On topic: libunistring is required- it's specified multiple times in README and cmakelist. if pcre is fine I don't see the reason to change it.

yochananmarqos commented on 2023-01-25 17:21 (UTC)

This is missing the libwebp dependency. I'm not sure that libunistring is required.

It looks for pcre first and if it can't find it then it looks for pcre2. I would change the dependency to the latter.

yochananmarqos commented on 2023-01-25 00:12 (UTC)

@Roshless: No, I won't create an account for a random mailing list. Yes, I will flag the package out of date.

That being said, nothing wrong with inviting community contribution via whatever method works best for you. I'm a package maintainer and don't always catch everything. I do appreciate it when a user lets me know I missed something so I can correct it.

Either way, package maintainers should already be signed up for release notifications from upstream to be notified of new versions. Flagging a package out of date both serves the purpose of letting the Maintainer know when a package is out of date and also let's users know one of their packages are out of date (with an AUR helper that has the feature).

TrialnError commented on 2022-06-08 11:52 (UTC)

It isn't entirely impossible to have different build steps for split packages. In such cases the source directory will be duplicated.
One example for such a split package is doublecmd from the repos.
I may take a look at this. Depends if I'm getting to my system, don't forget it etc :D

m040601 commented on 2022-05-29 15:36 (UTC) (edited on 2022-05-29 16:16 (UTC) by m040601) 

... and tried creating separate package for clagrange,...
....  now I'm even wondering how it's building ...
...

I must also add that the Lagrange developer is very receptive and willing to help and troubleshoot any issues attempting this.

Although he doesnt like github, he mirrors Lagrange there. And responds to issues there.

I had opened an issue regarding "clagrange" and "lagrange-bin" previously, https://github.com/skyjake/lagrange/issues/508

Might be usefull for future AUR maintainers.

... I'm planning to make a binary TUI release, too, but I want to polish it still a bit more....

Regarding the "AppImage" and "Flatpaks" binaries he releases:

    On Archlinux it fails with "segmentation fault". ... meant to be used only on Ubuntu right ? ...

... It's not Ubuntu-specific, however AppImages are not fully self-contained so it's not universal either

And,

    wanted to install some man page in root "/", like "/lagrange/resources.lgr" and "/man/lagrange". Probably needs some adjustment.

Oops, let me fix that...

1 2 3 4 5 6 7 Next › Last »