-
Notifications
You must be signed in to change notification settings - Fork 28
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
instructions on getting a specific holonix version #421
instructions on getting a specific holonix version #421
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
ops, i was too quick. i realize now that the context of these commands are not in a checkout of the holochain repository. hence, the version paths which assume that won't work in any other case. solutions are either make that context explicit or give absolute URLs to github.
Darn, I was hoping nix was more magical than that. (thanks @ThetaSinner for catching the complete absence of |
It's open source, any magic you feel is missing can be added. You could create a version that always assumes relative paths point to Holochain :) But yeah, it's simpler to reference derivations from inside the repo than from outside unfortunately. Nothing too crazy syntax-wise at least, just some long commands. Something else it would be good to document somewhere at some point is an answer to the questions "You modified Holochain for me, how do I run that from your branch?" and "You modified the HDK for me, how do I use that in my happs before you merge your changes". These are questions I've had several times, and the answer is often "The change is going into develop so you need a happ based on 0.3.x to be able to use it" but it does happen that people running on 0.3.x would be happy to test things, but it's not obvious how to do it. So when I say we should document it, what I actually mean is that somebody should push figuring out how to the top of my priority list so we can document it 😁 |
@pdaoust Do you have what you need from me to finish this off? I'd love to see this deployed so I can point people at it :) |
@ThetaSinner I do, thanks -- I'm going to change the examples to reflect that 0.2 is the default now though. |
Co-authored-by: ThetaSinner <ThetaSinner@users.noreply.github.com>
Gregory made Stefan's requested changes for me.
(plus a capitalisation fix)