⚒Anvil
Sign in

clo / cl-site public

closed

WIP: Add extra implementation when committing to extra-impls branch. 71

opened by common-lisp.net

Dave Cooper (@dcooper) on GitLab, 2018-10-22.

0 commits, 0 files changed

Ccommon-lisp.net

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-22.

Hmm. This is pretty ugly, IMO. I don't think we should depend on infrastructure defined in any particular user's home directory. Also, this isn't portable in the sense that it can't be executed "at home". Maybe it's better to allow passing a Makefile variable to override which SBCL binary will be used (i.e. a path-specifying variable)?

common-lisp.net added 5 commits <ul><li>ffab1cea - 1 commit from branch <code>clo:extra-impls</code></li><li>da974fbd - Resolve #25 in clo/cl-site.</li><li>87380ce9 - added extra implementations for pipeline on extra-impls branch.</li><li>4f5cec43 - fixed typo.</li><li>340d1892 - pulled from remote</li></ul> [Compare with previous version](https://gitlab.common-lisp.net/clo/cl-site/merge_requests/71/diffs?diff_id=856&start_sha=663884876cf9e2aac124fa8fbe8d9fe7ebc3c60e)
Ccommon-lisp.net

Dave Cooper (@dcooper) on GitLab, 2018-10-22.

Yep I know it's ugly. I kind of just threw it down as a straw man to get us talking. And there's no rush on it; feel free just to leave this sit here and keep working on content or other more pressing things. Maybe change this to WIP.

So from what I know there are like three issues:

  1. The implementations should be installed somewhere central rather than in someone's home directory. @root, Could you copy them somewhere official? I don't think I have Linux permissions to do that. Or, should we be keeping them in a repository? (they already came from Roswell, who is maintaining that repository for us, so that might seem a bit redundant to do it again ourselves..)

  2. The Makefile currently is not appropriate for any volunteers to run at home (including ourselves). How would your variable idea work? How would that work for the CCL or other implementations which also use different command-line options?

  3. My bin/sbcl startup script is super ugly - I know that can't be the "right" way to start up sbcl from a specified path...

common-lisp.net marked as a **Work In Progress**
common-lisp.net closed

Sign in to comment.