-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add rust toolchain and retris package #1
Conversation
@LinusCDE No oxide configuration? |
Add oxide info to retris
Thanks for your work on this @LinusCDE. Will review as soon as possible. |
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.
Apart from this minor suggestion, everything looks good to me!
package/retris/package
Outdated
license=MIT | ||
|
||
origin=https://github.com/LinusCDE/retris.git | ||
revision=0.5.3-1 |
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.
For security, I’d suggest putting the whole SHA-1 ID of the targeted commit here. If someone takes control of your repository, it’s easy for them to make the 0.5.3-1 tag points to different, potentially malicious code. This is harder to do with the commit ID, although attacks against SHA-1 are not unknown of.
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.
That's a very good idea. I even changed the tag sometime later to the latest commit, because I accidentally committed my custom ipkg. So yeah. They are very changeable which shouldn't be allowed here, indeed.
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.
Perfect! Thank you.
Hi,
see the commits for more info.