-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature request: Support non-binary AUR package using crates.io as source #28
Comments
This is a good idea. Let's move forward with it. The current default is to produce a
|
I see what you mean about the commands. I see no need to change the existing defaults from what you've set, am happy for this to be a new flag. In terms of an overhall, this could also be a good opportunity to upgrade to |
Now then: what should the new flag be callled? Off the top of my head:
|
Took some time to think about this. Combining the two suggestions of --source and --no-bin, we could do; New flag
New flag
This would allow two new combination I also wanted to note that to calculate the checksums for the crates.io build, we'll need to actually download the crate. Do you have a preference on how this is implemented, we could use curl, makepkg itself but it's a bit awkward since it needs a pkgbuild first, or a rust library like libcurl or reqwest. |
These are good suggestions. Let's move forward with both of them.
Let's be a good Unix tool and just call |
G'day,
Thanks for the crate!
I was wondering if you'd be open to the option of supporting crates.io as a source (e.g https://wiki.archlinux.org/title/Rust_package_guidelines#Source). In this case, I wouldn't need a binary build, I'd just be using cargo-aur to generate the PKGBUILD.
Let me know your thoughts on this, I'd be happy to have a go at contributing.
The text was updated successfully, but these errors were encountered: