-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prerequisites review reminder wrt jpm #30
Comments
Janet's Makefile acquired a new target named One thing worth noting might be that if one uses Recently I've been using:
to intall janet, so for jpm installation I would do:
One reason to use Suppose I want to test version A and version B of janet. I can install version A of janet for user X and test there. I can also install version B of janet for user Y and test there separarely. So at least for people who need to investigate issues related to versions, it's much nicer to be able to have multiple installations of something within a single OS -- and currently, a relatively cheap and straight-forward way to do this is with multiple accounts if the software in question can be made to function installed in a variety of locations. One can also use virtual machines (like VirtualBox), Docker, or NixOS / guix for this sort of thing. They all have their various trade-offs. |
For now I added a note that the user has to install jpm. I've removed notes about prefix for now, those were mostly for when I was replacing regular jaylib. Now freja-jaylib is a separate package. I'll link to this issue if someone wants to do it with prefixes, thanks for the details. :) |
jpm doesn't currently come with a git clone of janet's repository.
As far as I know, it's not quite clear how folks are going to be expected to install it yet.
This issue is just a reminder to revisit the prerequisites section of the README if separate installation of jpm becomes the norm.
The text was updated successfully, but these errors were encountered: