APKBUILD examples:Rust - Revision history

Tgirl: /* Considerations */ fix typo

2026-03-01T13:32:51Z

Considerations: fix typo

← Older revision		Revision as of 13:32, 1 March 2026
Line 5:		Line 5:
	One may encounter an issue when a package refuses to build using <code>cargo-auditable</code>, but successfully builds with <code>cargo</code>. This is because <code>cargo</code> itself exposes faulty data. More info can be found [https://github.com/rust-secure-code/cargo-auditable/issues/124 here].		One may encounter an issue when a package refuses to build using <code>cargo-auditable</code>, but successfully builds with <code>cargo</code>. This is because <code>cargo</code> itself exposes faulty data. More info can be found [https://github.com/rust-secure-code/cargo-auditable/issues/124 here].

	Most Rust projects use <code>cargo</code> to fetch Rust library dependencies. The current convention is to use <code>options="net"</code> fetch these during the <code>prepare()</code> phase. Use the <code>--locked</code> flag to ensure that the exact same versions of dependencies are fetched on each rebuild. If a package is missing a lockfile, include one with the aport and attempt to recommend upstream to include one.		Most Rust projects use <code>cargo</code> to fetch Rust library dependencies. The current convention is to use <code>options="net"</code> to fetch these during the <code>prepare()</code> phase. Use the <code>--locked</code> flag to ensure that the exact same versions of dependencies are fetched on each rebuild. If a package is missing a lockfile, include one with the aport and attempt to recommend upstream to include one.

	== Examples ==		== Examples ==

StrangePerson: add info about an issue with cargo-auditable, fix typo

2025-10-29T18:40:35Z

add info about an issue with cargo-auditable, fix typo

← Older revision		Revision as of 18:40, 29 October 2025
Line 3:		Line 3:
	Use <code>cargo-auditable</code> to encode dependency information into binaries.		Use <code>cargo-auditable</code> to encode dependency information into binaries.

	Most Rust projects use <code>cargo</code> to fetch Rust library dependencies. The current convention it to use <code>options="net"</code> fetch these during the <code>prepare()</code> phase. Use the <code>--locked</code> flag to ensure that the exact same versions of dependencies are fetched on each rebuild. If a package is missing a lockfile, include one with the aport and attempt to recommend upstream to include one.		One may encounter an issue when a package refuses to build using <code>cargo-auditable</code>, but successfully builds with <code>cargo</code>. This is because <code>cargo</code> itself exposes faulty data. More info can be found [https://github.com/rust-secure-code/cargo-auditable/issues/124 here].

			Most Rust projects use <code>cargo</code> to fetch Rust library dependencies. The current convention is to use <code>options="net"</code> fetch these during the <code>prepare()</code> phase. Use the <code>--locked</code> flag to ensure that the exact same versions of dependencies are fetched on each rebuild. If a package is missing a lockfile, include one with the aport and attempt to recommend upstream to include one.

	== Examples ==		== Examples ==

Sertonix: use CHOST instead of CTARGET like in the latest newapkbuild

2025-10-05T12:51:44Z

use CHOST instead of CTARGET like in the latest newapkbuild

← Older revision		Revision as of 12:51, 5 October 2025
Line 25:		Line 25:
	default_prepare		default_prepare

	cargo fetch --target="$~~CTARGET~~" --locked		cargo fetch --target="$CHOST" --locked
	}		}

WhyNotHugo: Document fetching of deps

2025-10-05T09:36:06Z

Document fetching of deps

← Older revision		Revision as of 09:36, 5 October 2025
Line 2:		Line 2:

	Use <code>cargo-auditable</code> to encode dependency information into binaries.		Use <code>cargo-auditable</code> to encode dependency information into binaries.

			Most Rust projects use <code>cargo</code> to fetch Rust library dependencies. The current convention it to use <code>options="net"</code> fetch these during the <code>prepare()</code> phase. Use the <code>--locked</code> flag to ensure that the exact same versions of dependencies are fetched on each rebuild. If a package is missing a lockfile, include one with the aport and attempt to recommend upstream to include one.

	== Examples ==		== Examples ==

WhyNotHugo: Add some outgoing links

2025-08-28T08:58:03Z

Add some outgoing links

← Older revision		Revision as of 08:58, 28 August 2025
Line 43:		Line 43:
	"		"
	</pre>		</pre>

			== See also ==

			* [[APKBUILD examples]]
			* [[Creating an Alpine package]]

	[[Category:Development]] [[Category:Rust]]		[[Category:Development]] [[Category:Rust]]

WhyNotHugo: Create page with minimal example

2025-08-28T08:55:50Z

Create page with minimal example

New page

== Considerations ==

Use <code>cargo-auditable</code> to encode dependency information into binaries.

== Examples ==

=== Basic example ===

<pre>
maintainer="Hugo Osvaldo Barrera <hugo@whynothugo.nl>"
pkgname=harper
pkgver=0.59.0
pkgrel=0
pkgdesc="Grammar checker that respects your privacy"
url="https://github.com/elijah-potter/harper"
arch="all"
license="Apache-2.0"
makedepends="cargo-auditable rust"
source="harper-$pkgver.tar.gz::https://github.com/elijah-potter/harper/archive/v$pkgver/harper-$pkgver.tar.gz"
options="net"

prepare() {
default_prepare

cargo fetch --target="$CTARGET" --locked
}

build() {
cargo auditable build --release --frozen
}

check() {
cargo test --frozen
}

package() {
install -Dm755 target/release/harper-cli "$pkgdir"/usr/bin/harper-cli
install -Dm755 target/release/harper-ls "$pkgdir"/usr/bin/harper-ls
}

sha512sums="
e5be781b33ba624e2447464a51ff8c0b565a42d7bf957c2fd6655f4bf312211fcf669bbb152b62a57494f89fd7fbee7eda37bbbaf7a61c5d4c8c9684ffe687bd harper-0.48.0.tar.gz
"
</pre>

[[Category:Development]] [[Category:Rust]]