-
Notifications
You must be signed in to change notification settings - Fork 183
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
Switch plugin packages back to git submodules #678
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.
Shame but yes this is long overdue
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.
You're right, and I apologize for leaving it like this for so long. Thanks for rectifying my oversight.
@Corecii @Kampfkarren you can write to this repo, right? What do we think, is this PR alright? It unblocks publishing releases (and indeed, last release was not published), so it seems kind of urgent to me! |
I think doing this to unblock releases is reasonable. I think we should look to use Wally in the future, but it's missing features that make it easy for us. It would be beneficial to make feature requests on the wally repo for what we need. I can see something like a wally crate with smarter download behavior working fine as part of a build script. |
Alright, so I hate to be the one to do this, but rojo-rbx#584 broke crates.io publishing and also caused librojo to be unusable. I see that there was some discussion on Discord shortly after the problem was realized, but there was no action taken. I think keeping librojo and publishing working far, far outweigh any convenience added by Wally. I've kept the same `Packages` naming convention to keep the diff minimal.
Alright, so I hate to be the one to do this, but #584 broke crates.io publishing and also caused librojo to be unusable. I see that there was some discussion on Discord shortly after the problem was realized, but there was no action taken.
I think keeping librojo and publishing working far, far outweigh any convenience added by Wally.
I've kept the same
Packages
naming convention to keep the diff minimal.