Docs: Add a tutorial dedicated to the "default plugin + multiple binaries" scenario

Metadata

Project: snapcraft
Number: #5040
Type: issue
State: open
Author: sed-i
Labels: —
Created: 2024-09-14 01:05 AM UTC
Updated: 2024-09-14 03:56 AM UTC
Closed: —

Current evaluation

Docs request: tutorial for packing multiple Go/Rust binaries with the plugin and iterating parts to discover/prime them. Unlabelled, no maintainer response; docs/tutorials still only has craft-a-snap, so unimplemented.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and zero comments in 748 days, so it has never been assessed by a maintainer, which is the default needs_triage condition. Investigation confirms the gap is real and unaddressed: docs/tutorials/index.rst toctrees only craft-a-snap, and grep for 'multiple binaries' returns no matches, while the existing craft-a-go-app.rst/craft-a-rust-app.rst how-tos cover only single-binary examples and never mention organize: or discovering additional binaries. It is not stale or superseded: the referenced 'iterating over a build' page content still exists (docs/how-to/debugging/debug-a-snap.rst, section 'Iterate on the build lifecycle', covering --shell/--shell-after/--debug), so the request is partly already covered elsewhere but the dedicated tutorial is still missing.

Evaluated by: mr-cal-bot

Impact: 35 Quick Win: 17 Complexity: 30 Confidence: 85 Actionability: 68

Issue body

### What needs to get done Go and rust projects often pack perfectly fine by using the plugins. Often, there are multiple binaries produced by `go build` or `cargo build`. Please add a tutorial that walks users through: 1. Setting up a minimal `snapcraft.yaml` that uses just the plugin. 2. [Poking](https://snapcraft.io/docs/iterating-over-a-build) through the parts as they are built in search of the binaries. I.e. how am I supposed to know to use `command: bin/my_app`? And what about other binaries? I'd like to see what are their names and prime (?) them as well. Just as an example, moving from using the plugin as is, to packing several binaries is [not trivial](https://github.com/sed-i/nushell-snap/commit/3c174608c50665846f333a6d59537bffa0a27aba). Almost every line in that diff went through a failed pack. ### Why it needs to get done Craft-parts can be challenging to grasp, so it would help a lot to have a basic tutorial that guides the user through a discovery process.

Evaluation history

Date	Model	Scores	Action	Summary
2026-10-02 05:18 PM UTC	stealth/space-bunny-alpha	Impact: 35 Quick Win: 17 Complexity: 30 Confidence: 85 Actionability: 68	needs triage	Docs request: tutorial for packing multiple Go/Rust binaries with the plugin and iterating parts to discover/prime them. Unlabelled, no maintainer response; docs/tutorials still only has craft-a-snap, so unimplemented.
2026-09-20 04:35 PM UTC	qwen/qwen3.6-35b-a3b	Impact: 30 Quick Win: 17 Complexity: 20 Confidence: 75 Actionability: 70	needs triage	Documentation request for a tutorial on packing multiple binaries with Go and Rust plugins in snapcraft.yaml
2026-09-01 03:04 AM UTC	qwen/qwen3.8-27b	Impact: 35 Quick Win: 24 Staleness: 85 Complexity: 30 Confidence: 70 Support Request: 10	needs triage	Request for a tutorial covering the 'default plugin + multiple binaries' scenario (Go/Rust projects producing several binaries). Open 717 days, no labels, no comments, no maintainer acknowledgement. No such tutorial exists in docs/tutorials or docs/how-to.
2026-07-22 12:14 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 20 Confidence: 85 Support Request: 10	close stale	Request to add documentation/tutorial for using default plugin with multiple binaries in Go/Rust projects. Issue is 676 days old with no activity or maintainer response.
2026-07-08 05:56 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 15 Confidence: 70 Support Request: 5	needs triage	Request for a tutorial on configuring snapcraft to build and prime multiple binaries using default plugins for Go and Rust projects. Unaddressed for over 1.5 years with no maintainer interaction.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.