Package Details: elinks-git 0.18.0+r7367+g4b979b47e-1

Git Clone URL: https://aur.archlinux.org/elinks-git.git (read-only, click to copy)
Package Base: elinks-git
Description: An advanced and well-established feature-rich text mode web browser. Git version, JavaScript disabled.
Upstream URL: https://github.com/rkd77/elinks
Keywords: browser devel textmode web
Licenses: GPL-2.0-only
Conflicts: elinks
Provides: elinks
Submitter: ferreum
Maintainer: None
Last Packager: envolution
Votes: 5
Popularity: 0.90
First Submitted: 2017-01-18 20:19 (UTC)
Last Updated: 2025-01-14 20:30 (UTC)

Required by (14)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

envolution commented on 2025-01-14 22:35 (UTC)

Thanks mate, I clearly overlooked that comment. I'll work on it

micwoj92 commented on 2025-01-14 22:20 (UTC)

On AUR wiki page: https://wiki.archlinux.org/title/Arch_User_Repository#Flagging_packages_out-of-date

envolution commented on 2025-01-14 22:05 (UTC)

I don't disagree, that's something I'm still working on - the goal being only bumping on minor/major version changes. I am curious though, where specifically is it discouraged because I did spend time trying to find out some months ago what the policy was regarding this

micwoj92 commented on 2025-01-14 21:45 (UTC)

Such bumps for -git packages are pointless and discouraged: https://aur.archlinux.org/cgit/aur.git/commit/?h=nethack-git&id=091d1e54df0040861aea5873f8a9e3817afdf852

It should only be bumped when something else changes, because pkgver is not a constant in this case.

envolution commented on 2025-01-14 21:29 (UTC)

Close, it checks every 12 hours against all of my maintained packages for upstream version changes, or in the case of the git packages - if there are any new commits, and tries to compile them. If they compile successfully I update the version on here.

If you're curious to see how, all of it is done from github actions, and the scripts are linked in my profile

micwoj92 commented on 2025-01-14 21:01 (UTC)

Thanks for the explanation, I am not quite sure I understand second paragraph. Do you mean that you have CI that builds packages when new commit is pushed upstream?

envolution commented on 2025-01-14 20:50 (UTC)

@micwoj92 it's not required, just part of my current CI process - technically nvchecker files are pointless for every package on AUR

I use them personally to externally compile every -git package I maintain so I am aware when things fail so I can look into them, and I find the process interesting. The nvchecker files I create are used to ensure I'm not testing a repo that has not had a recent commit

Since I have them, I thought it would be nice for future maintainers to have them when they take over packages I would no longer maintain as they may find them helpful for maintenance tasks

micwoj92 commented on 2025-01-14 20:39 (UTC)

Isn't nvchecker pointless for -git packages?

ferreum commented on 2022-04-21 17:19 (UTC)

@firegem git is now in makedepends.

I also changed the URL to use the master branch instead of version-0.14.

From my attempt of using it, there currently seems to be a problem with background color, so you may want to locally change it to tag=v0.15.0 or similar for now.

firegem commented on 2022-04-21 05:47 (UTC)

This needs git as a makedep or it fails to compile in a chroot.

1 2 3 4 Next › Last »