libera/#commonlisp - IRC Chatlog
Search
6:09:36
hexology
what would cause the error `Component :CL-BASE64 not found, required by #<SYSTEM "hunchentoot">` when running `(asdf:load-system "hunchentoot")` under qlot+roswell?
6:12:24
hexology
and the qlfile has `ql hunchentoot 2021-04-11` and `ql chunga 2021-04-11` (wasn't sure about the right dates to use)
6:15:19
hexology
am i misusing qlot? it looks like it's not installing dependencies when i run `qlot install`
6:27:03
hexology
i must be doing something wrong that's very simple, i have read all the qlot and roswell docs several times
10:45:13
selwyn
for me, it is C:/Users/selwyn/quicklisp/local-projects/ on a fresh quicklisp install
10:47:13
selwyn
though for actual development i use the portacle quicklisp installation which is itself under the msys2 home directory
10:57:59
tfb
shka: my point was, you don't need to: write a program which uses that variable. If you need, say, to run programs in some other language to install things there, spawn them from CL
11:11:13
selwyn
if you are deploying it is not wise to rely on or expect the existence of quicklisp though
12:07:57
ludston
In your lisp init file, (e.g. .sblrc) it will specify the directory that quicklisp is installed in. By default this is (user-home-pathname) which on Windows uses the "HOME" environment variable.
12:09:03
ludston
I'm not sure what (user-home-pathname) is by default because mine is set to my msys64 home dir
12:13:55
ludston
If you are using lisp on Windows, I'd highly recommend using something like msys, because a lot of libraries rely on open source dll's. You can set your "Path" environment variable to point to C:\msys64\mingw64\bin and then install external dependencies with pacman
12:15:32
selwyn
when i start sbcl under msys64, it does indeed instead install quicklisp under the msys64 homedir
12:16:18
selwyn
it´s best to just stick to doing everything under msys, and you also get a shell to use
12:17:06
ludston
If you open up "Edit the system environment variables" you can set the HOME directory so that it is always msys, even if you launch sbcl outside of msys
12:20:55
Duuqnd
I'm probably not doing that myself though because my Windows computer is already messed up with like three different msys/mingw things installed somehow
12:21:41
splittist
My problem (on Windows) is not lisp and its idea of home (/Users/me), it's emacs and it's weird idea (:
12:22:16
tyson2
I'm just getting started with sbcl on windows, and have it working with slime, etc. But I've decided to set up a local docker sbcl instance and use that instead.
12:24:29
tyson2
that way I can avoid all the drawbacks of adding linux-workalike libraries for sbcl on windows which I have already encountered
12:26:09
tyson2
seems to be good support for docker in emacs, docker-tramp etc., will test it out this weekend
12:27:12
ludston
Deployment on windows is only easier when everybody copies the same .dll into every separate install
12:28:46
tyson2
eventually I will skip the local container and just develop directly on the docker sbcl instance on the vps
12:30:37
tyson2
on AWS lightsail, you can now deploy docker instances directly, without first installing linux
15:04:21
Josh_2
Shinmera: After saving my content to a temp file with the correct extension, I am using the :media key and tracing error, I get the following: https://plaster.tymoon.eu/view/2488#2488 sorry its a bit vague but this is out of an in use system
15:10:48
Josh_2
Is doing a (ql:quickload :chirp-dexador) enough to swap over to the dexador backend?
15:16:40
Josh_2
just says :expected-type character :context :aref, cant read the rest because my terminal doesn't scroll back that far
15:41:10
Gnuxie
could it be dexador's equivalent to drakma's text-content-types that needs to be set?
16:53:51
hexology
why does quicklisp/qlot use dates instead of the :version specified in the system?
16:54:31
hexology
Xach: i was under the impression that i can only specify a quicklisp release date in the qlot file, as opposed to a version number
16:54:52
Xach
hexology: I don't know about qlot. quicklisp releases are versioned with a date. there is no system involved.
16:55:14
Xach
The date is not processed as a date, really - it's just a convention with convenient ordering properties usually.
16:55:22
hexology
right, but does quicklisp itself have no facility for checking the version numbers?
16:55:52
hexology
pretty much every other package manager i've seen uses the version number, so i assume there's a good technical reason why quicklisp doesn't work like that
16:56:29
Xach
Every project is snapshotted, built, and released together. Projects are not updated individually.
17:01:06
Xach
hexology: i mean if something doesn't build, i tell the author, and they try to fix it, and then everything is built again.
17:02:55
hexology
i see, i didn't realize manual work was being done to validate that they all build together
17:03:19
hexology
by comparison, npm, pypi, etc. would be "rolling release" where the author can publish a new version at any time
17:03:20
Xach
it's pretty automated, but there's a bit of manual work to plug the failure logs into github or other bug report systems.
17:03:42
Xach
there are advantages to rolling releases too - i don't mind if people don't like how quicklisp works, there are different ways to do things.
17:04:00
hexology
it's not that i don't like it, it's that it's very unusual for a programming language package manager
17:04:49
hexology
what if there's a bug and a developer wants to publish a quick fix? do people just have to install from git, or is it case-by-case where you might do a 2nd release?
17:05:58
Xach
hexology: there are a few options for the user. 1. don't update to the new dist 2. override with a local version from git or whatever. I rarely, rarely make a quick new release of everything - I've done it when slime crashed on startup, once, but fewer than 5 times in 10 years.
17:06:59
Xach
i don't know if it has the indelible release policy or not, but i consider that a feature too