So… I am (re)building from source with make. Note that I previously raco pkg update --clone drraket. Now, I keep getting this error:
/Users/sorawee/git/racket-repos/drracket/drracket/drracket/private/debug.rkt:1238:44: drracket:init:system-inspector: unbound identifier
in: drracket:init:system-inspector
compilation context...:
/Users/sorawee/git/racket-repos/drracket/drracket/drracket/private/debug.rkt
system-inspector was recently added by @robby if I’m not mistaken, and when I view the source, they are there, so I don’t know what went wrong
I suppose you did git pull in racket/racket first maybe, then make, then git pull in racket/drracket, then raco setup?
I am not sure what’s going wrong but I did add that somewhat recently yes. I certainly have the same raco pkg update --clone setup in drracket and am not seeing that so something is different between our setups.
Yeah, I did try all of that… :disappointed:
Just to check, what does (collection-file-path "init.rkt" "drracket/private") report?
#<path:/Users/sorawee/git/racket-repos/drracket/drracket/drracket/private/init.rkt>
How about (collection-file-path "drsig.rkt" "drracket/private")?
(Is drracket-plugin-lib installed at the same clone?)
Interesting! It returns #<path:/Users/sorawee/git/racket/racket/share/pkgs/drracket-plugin-lib/drracket/private/drsig.rkt>
So while drracket-plugin-lib exists at /Users/sorawee/git/racket-repos/drracket
raco pkg update --clone doesn’t switch to use the newly cloned one
So when you ran raco pkg update --clone originally, raco pkg update didn’t offer to move drracket-plugin-lib to the clone?
I thought it did, and I thought that I said yes…
In any case, how do I unscrew myself?
i think probably raco pkg update --clone /Users/sorawee/git/racket-repos/drracket/ drracket-plugin-lib
Thanks, will try that.
Is there a ‘standard’ or preferred academic paper to reference when referring to Racket generally? In something I am writing, I mention that I used Racket, and would like to include an appropriate reference. E.g. “Racket [reference] was used to implement XYZ.”
@techreport{plt-tr1,
title = {Reference: Racket},
author = {Matthew Flatt and PLT},
number = {PLT-TR-2010-1},
institution = {PLT Design Inc.},
year = {2010},
note = {\url{<https://racket-lang.org/tr1/}>}
}
Thanks :slightly_smiling_face:
That’s right for Racket as a piece of software. If you want to cite the general ideas behind Racket, I would choose our 2018 CACM article, or the Racket Manifesto from SNAPL
‘As a piece of software’ is probably the correct interpretation for this particular instance. I would appreciate links to the other articles you mention, though, if you are able to dig them up please.