Search Criteria
Package Details: guile-wisp-hg r1710.ad2b1867648a-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/guile-wisp-hg.git (read-only, click to copy) |
---|---|
Package Base: | guile-wisp-hg |
Description: | Whitespace to Lisp converter (srfi-119) as a guile module |
Upstream URL: | http://www.draketo.de/english/wisp |
Keywords: | guile |
Licenses: | GPL3+ |
Provides: | wisp |
Submitter: | tantalum |
Maintainer: | Jarhmander |
Last Packager: | Jarhmander |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2017-08-19 14:37 (UTC) |
Last Updated: | 2020-09-20 13:35 (UTC) |
Dependencies (2)
- guile (guile-gitAUR)
- mercurial (mercurial-hgAUR, mercurial-stable-hgAUR) (make)
Latest Comments
Jarhmander commented on 2020-09-20 13:44 (UTC)
Sorry for the delay, I was out of town. Meanwhile, tantalum forwarded an email from the developer (Arne) that has the necessary information.
The package is now updated and appears to work fine on guile-2.2.
Jarhmander commented on 2020-09-14 14:06 (UTC)
I'll notify the original developer about this situation. I don't know where the last updated upstream repo is anymore.
micwoj92 commented on 2020-09-08 19:52 (UTC)
Bitbucket no longer supports mercurial repositories, could you please update this package?
Jarhmander commented on 2019-06-07 18:50 (UTC)
Ok then, that's sad. Thank you for maintaining this package. I just adopted it, and I'll update it as soon as I can.
I remember having seen this on my Pinebook that runs another distro. I know it's because somehow,
GUILE_TOOLS
isn't defined, I just don't know why yet.It might be because of the .SRCINFO file; it must be updated as well.
Hmm... Well that's probably because the tabs didn't make through the pastebin? If they get converted to spaces the patch won't apply cleanly. Sorry about that.
tantalum commented on 2019-06-05 18:52 (UTC) (edited on 2019-06-05 18:52 (UTC) by tantalum)
i applied the patch for the default branch. i would like to disown the package, so if you like you could take over.
Jarhmander commented on 2019-06-04 23:07 (UTC) (edited on 2019-06-04 23:08 (UTC) by Jarhmander)
The branch "stable" is rather old; I'm hesitant to flag the package.
The "default" branch compiles the scm files so there are no more compile warnings when using the language. However, both the old (stable) and new version suffer from packaging issues (all from upstream, the PKGBUILD is not at fault)... I contacted the developer, which prompted the recent post in its blog, but I'm afraid he will not look into this anytime soon. Anyways, here's the matter:
A smaller issue is that the PKGBUILD doesn't appear to conform to good packaging standards. For instance, the package should be build in the
build
function. Also, you forgot to put the maintainer's info (you!) in the top.This git patch will fix the "stable" version: https://pastebin.com/raw/LDnW5JXL ; this git patch will update the PKGBUILD to the latest "default" version: https://pastebin.com/raw/vu43vm1b , which will probably break once the developer fixes its repo.
(none of these patches put the maintainer info in the top)