Hm, I think maybe i will just abort this effort on my system since it seems
like Matthew is already kinda working on making this exact thing better (as he
said earlier) at https://github.com/racket/racket/commit/dfbb7040a
I'll just use user scope now and wait until this kind of thing is
To be clear:
"/opt/Racket/Racket 8.1" is the system racket which the unprivileged user
cannot write.
"/opt/Racket/Packages/8.1" is a unprivileged-writable directory intended for
use as a package destination.
Nate
> On May 20, 2021, at 3:55 AM, Nathaniel W Griswold
> wrote:
>
> Oh, and i'll
Oh, and i'll just duplicate the issue here for Matthew / the Racket side since
it could just be racket related:
The errors i ran into are when using a custom PLTCONFIGDIR with this
config.rktd:
---
#hash((build-stamp . "")
(catalogs
.
Sam,
Yes, the tool and PLTCONFIGDIR help me better control things. I think the tool
is helpful. I ran into a problem with racket trying to delete files and posted
it on github at https://github.com/samdphillips/raco-pkg-env/issues/3
I don't think it's really a raco-pkg-env issue, though, i
You might also be interested in the new `raco-pkg-env` tool:
https://github.com/samdphillips/raco-pkg-env/
Sam
On Tue, May 18, 2021 at 12:20 PM Matthew Flatt wrote:
>
> Yes, this approach can work. I don't think the existing Racket tools
> will help much with persisting a configuration across
Yes, this approach can work. I don't think the existing Racket tools
will help much with persisting a configuration across versions, though,
so you'd probably have to script that.
One potential drawback of your approach is that executables,
documentation, etc., associated with the extra package
Hello,
I was setting up Racket on my linux box and i realized that there are a lot of
options for path configuration and i forgot a lot of what i discovered last
time i dug into this. I was trying to set up installation scope but maybe a
little cleanly and figured someone might have some
7 matches
Mail list logo
