-
Notifications
You must be signed in to change notification settings - Fork 17
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
Change parsec version to 1.3.0 #164
Change parsec version to 1.3.0 #164
Conversation
3862e99
to
8108f7b
Compare
|
||
``` | ||
export PARSEC_TOOL="$(pwd)/parsec-tool" | ||
export PARSEC_TOOL="$(pwd)/target/debug/parsec-tool" |
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.
I think the context is using the quick start bundle where we have the built binaries.
So this change is not needed as it should be straight forward.
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.
The context here is:
If parsec-tool is not installed into a directory included in PATH, then you also need to define PARSEC_TOOL environment variable with a full path to it:
So that means that this is used to indicate how to do it if you are building or installing into a different path, no?
``` | ||
|
||
To run the script, simply execute it without any arguments as follows: | ||
To run the script, simply go to `quickstart-1.2.0-linux_x86_64/quickstart` and execute it without | ||
any arguments as follows: |
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.
Same as above.
Signed-off-by: Tomás González <[email protected]>
Signed-off-by: Tomás González <[email protected]>
8108f7b
to
74cd261
Compare
Signed-off-by: Tomás González <[email protected]>
74cd261
to
98eec99
Compare
Signed-off-by: Tomás González [email protected]