FS#72296 - [clisp] Upstream of clisp changed.
Attached to Project:
Arch Linux
Opened by shenlebantongying (shenlebantongying) - Thursday, 30 September 2021, 07:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
Opened by shenlebantongying (shenlebantongying) - Thursday, 30 September 2021, 07:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
|
Details
Description:
The master branch of clisp seems no longer host on SF. Steps to reproduce: When I try my new mac box, I noticed that the homebrew team use a different upstream for clisp. https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/clisp.rb#L5 It turns out belong to clisp's authors and there are some activities there. https://gitlab.com/gnu-clisp/clisp.git However, this is not urgent before the next clisp release. Also, the clisp from AUR changed url to there. |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:16 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/clisp/issues/1
Saturday, 25 November 2023, 20:16 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/clisp/issues/1
My experience is that avoiding defunct projects like this and using alternatives like SBCL makes life easier, happier, and less suffering.
This bug should be just closed. A new release/tag will never happen unless someone invests a lot of effort in forking the said project and making regular releases.
FS#79217. Closing this bug or pointlessly blaming upstream won't make the issue go away, which is: the current Arch version of this package is severely (5 years) outdated.https://gitlab.com/gnu-clisp/clisp/-/issues/21#note_521467279
It is the upstream's fault & problem & unhealthy maintainership (dependent on a single person).
Opening a bug here cannot solve it.
Upstream have to tag a new release.
Also, clisp-git exists in AUR.