freenode/#lisp - IRC Chatlog
Search
5:13:17
knobo
In my slime buffer, at the top, I have a line saying "SBCL Port: ... Pid: ...". How can I add (machine-instance) to that line?
9:23:11
loke
There is an SBCL-specific call in the CL-CLTL2 package, but is there some library that attempts to expose this?
9:28:34
jackdaniel
according to spdx it is not a libre license, so I'd personally avoid it (https://spdx.org/licenses/)
9:31:47
loke
It seems if I change it and distibute the changed version I need to change the package name. I can live with that.
11:56:48
jeosol
I have recently tried to setup an ec2 instance manually CL, it was a pain. Does anyone have an automated setup?
11:57:35
jeosol
primary I use SBCL and had to bootstrap it with CCL, I must be doing something wrong, or not aware of betters ways to set this up
11:58:27
jeosol
I would need a better way, I want to essentially, push my setup to the bare aws ec2 and have things almost good to go (of course push lisp code, etc)
11:59:46
jeosol
I have data, other executables (some to run with wine), files, etc to be able to run. Some dude on aws reddit suggested I set up on instance, take a snapshot, then I can replicate that instance. It has been a pain to set up one
12:01:30
jeosol
Besides setting up SBCL, quicklisp etc, I have to copy over some directories (with data), some other executables, and other minor stuff. e.g., have python available for some ML stuff.
12:02:05
jeosol
I would like to have a clean way to do this, even if a bit painful to setup. I will then create other instances of this setup for use later. This is my use case.
12:02:41
jeosol
_death: Thanks for the suggestion. at this time, I am not a docker expert, and it is something I am trying to learn, had it recommended a few times.
12:03:37
jackdaniel
putting aside lack of ability to install custom (hand-build lisp) it had problems with installing implementations supplied by itself
12:04:41
jackdaniel
jeosol: when you download SBCL release tarball you may extract it and call install.sh; prebuilt x86-64 binaries are supplied
12:04:50
jeosol
I spent so much time trying to install SBCL on the bare ec2 machine, tried cmucl (different versions, had errors), eventually ccl worked. then quicklisp, ..., I rather spend some time on a easier, less error prone set up now
12:05:29
jackdaniel
jeosol: I don't know why your instance doesn't work, but I'm succesfully using there extracted sbcl tarball with run_sbcl.sh script (without installing whatsoever)
12:05:31
jeosol
jackdaniel: yes, I did that intially, but when I run, I was getting some pid error main() function, and landing in ldb debugger or something
12:07:23
JuanDaugherty
don't install slime from the distro, i've never figure out how that's supposed to work
12:07:59
jeosol
I copied slime from my local setup, I don't plan to do much remote coding though (hopefully). Just need to move setup, run code there
12:09:58
jeosol
jackdaniel: SBCL works now, but the sbcl binary option was landing in ldb debugger with some main() functionstuff .
12:11:12
jeosol
shrdlu68: not sure I mentioned this, I eventually use the source and compiled with ccl
12:11:56
jeosol
basically, because of the huge dependencies for my setup, I want to have a way to automate most of the work
12:13:01
shrdlu68
jeosol: These days, the fashionable thing is to try and get a single executable if you can, or use tools like ansible or containers.
12:15:55
jeosol
Has anyone had to replicate cloud machine instances, if so what approach do you use. It may be better to setup one, test that it works, and get more instances from that if needed. Is this approach ok?
12:17:27
JuanDaugherty
ACTION prefers bash script independent of the hosting vendor, ec2-tools there
12:25:54
shrdlu68
Ansible might be more straight-forward. Have your code in some revision control, pull it and build it where you want.
12:29:11
jeosol
shrdlu68: It seems that is the option closer to what I was thinking. I have a repo on ec2 and can push the code there.