-
Notifications
You must be signed in to change notification settings - Fork 33
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
Is it possible to include some applets from toybox? #28
Comments
That would be cool! Based on my experience with c2rust so far, I think the easiest way forward is to do by-hand rewrites in rust for most new applets, but I'd be happy to consider PRs either way! Starting with fresh rewrites helps with the licensing situation as well. |
BTW, what is the licence of rustbox? |
It's kind of weird right now... Busybox is GPL and rustybox is obviously transpiled from that. I'm not a lawyer, so I guess I'm just letting users figure out however they'd like to interpret the situation. The end goal is to gradually split rustybox into cargo workspaces with each applet in its own project. Then to slowly rewrite things from scratch with a less viral license. |
I ported toybox file command to Go before, I think I can port it to Rust.
It would be cooler if rustybox has some handy commands like I don't know why they made |
No idea! Happy to have them in rustybox though! I think the ideal situation will be to split each of the applets into its own cargo workspace project. That way users can have very fine-grained control over what applets they'd like to compile and could mix-and-match their favorite rustybox distro. |
Is it possible to include some applets from toybox?
For example the file command
Toybox is BSD licence and Busybox is GPL licence, I don't know if they can be mixed together :/
The text was updated successfully, but these errors were encountered: