Search Criteria
Package Details: cargo-pkgbuild 0.2.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cargo-pkgbuild.git (read-only, click to copy) |
---|---|
Package Base: | cargo-pkgbuild |
Description: | ArchLinux PKGBUILD generator from Cargo.toml manifest |
Upstream URL: | https://github.com/kstep/cargo-pkgbuild |
Licenses: | Apache-2.0 OR MIT |
Submitter: | kstep |
Maintainer: | None |
Last Packager: | neitsab |
Votes: | 4 |
Popularity: | 0.22 |
First Submitted: | 2016-07-04 16:18 (UTC) |
Last Updated: | 2024-09-06 21:06 (UTC) |
Dependencies (2)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
Latest Comments
neitsab commented on 2024-09-06 21:13 (UTC) (edited on 2024-09-06 21:22 (UTC) by neitsab)
All right folks, I just updated the package.
I think this really ought to be a
-git
package, this would avoid having to pick a specific commit hash and use that in a custom variable because of it.Note though that the author has commented:
So this is unlikely to see much change.
I tried it on a simple package and it didn't do much better than a good old copy paste from a template Rust PKGBUILD, which I leave here for those interested:
I'll orphan this as I'm not expecting to be using it in the future.
AkechiShiro commented on 2023-07-07 22:27 (UTC) (edited on 2023-07-07 22:27 (UTC) by AkechiShiro)
Here is diff to update the PKGBUILD :
AkechiShiro commented on 2023-07-03 13:32 (UTC) (edited on 2023-07-03 15:35 (UTC) by AkechiShiro)
This package does not work at the moment, it spits back a Rust error :
Sorry this is an error upstream, it just needs a Cargo.toml files that contains metadata in the folder where you're running the command.
mdorst commented on 2022-07-19 09:02 (UTC)
This package has been fixed so that it now produces output consistent with the Rust package guidelines.
alerque commented on 2021-08-28 18:18 (UTC)
I adopted this because it sounded worth a try. I fixed up the packaging, but then I looked at what the upstream project in actually doing. The output of this program is so far from the Rust package guidelines that I do not recommend anyone use it! If upstream issues such as this one ever get addressed that could change, but for the moment using this will run afoul of so many guidelines that it would take more work to fix than to write properly from scratch.
I'm orphaning this again ... adopter beware.
kstep commented on 2016-12-16 09:31 (UTC)
jtojnar commented on 2016-12-14 00:36 (UTC)