Search Criteria
Package Details: clasp-cl-git 2.7.0.r1.g2c780f035-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/clasp-cl-git.git (read-only, click to copy) |
|---|---|
| Package Base: | clasp-cl-git |
| Description: | Bringing Common Lisp and C++ Together |
| Upstream URL: | https://github.com/clasp-developers/clasp |
| Licenses: | LGPL |
| Conflicts: | cando, cando-git, clasp-cl |
| Provides: | cclasp-boehm, clasp-cl, common-lisp |
| Submitter: | yitzi |
| Maintainer: | yitzi |
| Last Packager: | yitzi |
| Votes: | 1 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-05-21 23:22 (UTC) |
| Last Updated: | 2025-01-21 18:20 (UTC) |
Dependencies (16)
- boost (boost-gitAUR)
- clang (llvm-gitAUR, clang17-binAUR, clang-minimal-gitAUR)
- expat (expat-gitAUR)
- fmt (fmt-gitAUR)
- gmp (gmp-hgAUR)
- libbsd (libbsd-gitAUR)
- libedit
- libelf (elfutils-gitAUR)
- libffi (libffi-gitAUR)
- llvm (llvm-gitAUR, llvm-minimal-gitAUR)
- ncurses (ncurses-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- git (git-gitAUR, git-glAUR) (make)
- ninja (ninja-kitwareAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR, ninja-memAUR) (make)
- pkg-config (pkgconf-gitAUR, pkg-config-gitAUR, pkgconf) (make)
- sbcl (sbcl-gitAUR) (make)
Required by (29)
- cl-3bmd (requires common-lisp)
- cl-alexandria-git (requires common-lisp)
- cl-anaphora (requires common-lisp)
- cl-closer-mop (requires common-lisp)
- cl-colorize (requires common-lisp)
- cl-esrap (requires common-lisp)
- cl-fiasco (requires common-lisp)
- cl-html-encode (requires common-lisp)
- cl-ieee-floats (requires common-lisp)
- cl-ironclad (requires common-lisp)
- cl-iterate (requires common-lisp)
- cl-javascript (requires common-lisp)
- cl-local-time (requires common-lisp)
- cl-md5 (requires common-lisp)
- cl-named-readtables (requires common-lisp)
- cl-named-readtables-git (requires common-lisp)
- cl-parenscript (requires common-lisp)
- cl-parse-js (requires common-lisp)
- cl-pythonic-string-reader (requires common-lisp)
- cl-shop2 (requires common-lisp)
- Show 9 more...
Latest Comments
xiota commented on 2023-12-31 16:32 (UTC)
It looks like
kogamay be able to update an existing repo and checkout the desired commit. So shouldn't need any fancy prep besides the symlink.If you move the cloning from
prepare()tobuild(), some people may complain because supposedlybuild()isn't supposed to download anything. (I don't recall seeing it in any guideline though, and some build systems necessarily download stuff in the middle of the build.)yitzi commented on 2023-12-31 16:01 (UTC)
The build system clones repos with specific commits so I think the idea of replicating that into the source array is just going to be prone to breakage.
I'll look into reducing the cloning in prepare and moving that to build if possible.
xiota commented on 2023-12-31 15:40 (UTC) (edited on 2023-12-31 15:43 (UTC) by xiota)
Thanks for updating.
If you're open to reorganizing in the future, the build system might be able to work with symlinks to makepkg prepared folders.
aur/swift-languagedoes this.Bandwidth saving is significant, especially for automated rebuilds, because
prepare()runs beforepkgver(). So even if there is no change, the repos are recloned.yitzi commented on 2023-12-31 14:24 (UTC)
I've updated the version number and removed some of the repos not needed during build, but the build system cannot pull from the source array, so the rest will have to stay as is.
xiota commented on 2023-12-26 10:25 (UTC)
Some changes needed:
pkgdirinprepare()needs to be in quotes because it can contain spaces.pkgver()to use format#.r#.g#.Also, is it possible to prepare git subprojects using source array so they can be cached? Maybe just the big ones:
bdwgc,mps, andansi-test.lyhokia commented on 2022-01-14 11:30 (UTC)
Hello yitzi, I try to install this package, but when it's compiling, it eat up all my Memory and Disk IO usage, and then my PC is so busy that it won't respond to any input(mouse moves, keystrokes), that I have to physically power off my laptop. Can you help me troubleshoot what's going on here?