cargo-pkgbuild icon indicating copy to clipboard operation
cargo-pkgbuild copied to clipboard

ArchLinux's PKGBULD generator from Cargo.toml manifest file

Results 5 cargo-pkgbuild issues
Sort by recently updated
recently updated
newest added

This PR contains the following: 1. All functions now propagate their errors upwards. 2. Errors are now printed in `main` instead of `unwrap`ped 3. The Cargo.toml handling code is replaced...

The current `PKGBUILD` contains a workaround: ``` prepare() { cd "$_archive" # Upstream lockfile is buggered in v0.1.1 cargo update cargo fetch --locked --target $CARCH-unknown-linux-gnu } ``` I'm not sure...

To my understanding, #8 introduced changes to the behavior of this package. That should be accompanied with a version bump.

When using `cargo release`, unreleased commits will generate an invalid pkgver. The file currently has: `pkgver=0.12.1-alpha.0` `pkgver=0.12.1_alpha.0` should work however.

hi, according to [arch wiki](https://wiki.archlinux.org/title/Rust_package_guidelines#Notes_about_using_cargo_install), the `--no-track` argument should always be used, otherwise `cargo install` will create unwanted files such as `/usr/.crates.toml` or `/usr/.crates2.json`. thanks for `cargo-pkgbuild`, regards, lacsaP