-
Notifications
You must be signed in to change notification settings - Fork 20
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
[WIP] set up cargo #21
base: master
Are you sure you want to change the base?
Conversation
|
||
install: nucleus | ||
install nucleus /usr/local/bin/ | ||
|
||
test: test-dir test-zip test-app test-app-tiny | ||
|
||
test-dir: nucleus | ||
./nucleus ../../test/manual -- 1 2 3 | ||
./nucleus ../../tests -- 1 2 3 |
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.
Did you mean to revert these lines?
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.
nope!
We should probably move this to an org first so that we can have it host the repo for the new crate? |
I love love to move to an org. Just want a permanent name first. So far I'm leaning towards keeping "nucleus" and just ignoring the jokes about the tv show. |
do we think it should be the org's crate and not mine personally? i'm not sure i really care, checking to see if everyone else does. it doesn't matter where the crate is though, we use crates.io to serve it. the crate is already published. |
@ashleygwilliams yeah, an org place for crates will be great. This particular crate should go away anyway once we move the core main to rust. (we can then just call rust std lib directly). |
agree, that's why i figured publishing it under my github makes more sense |
fixes #19