Rust packaging FAQ #232
Open
Rust packaging FAQ #232
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work in progress, because the index hasn't been updated yet.
Description
This adds a Rust packaging FAQ. More than most language ecosystems, Rust packages tend to be described as exceptions to packaging policies and rules. The details of how Ubuntu makes use of the upstream Debian Rust packages is not obvious, especially with respect to
rustc. Moreover, many of the patches applied torustcaren't necessarily obvious.This FAQ is essentially an attempt to gather some of that overview information into a single place, and to ease the burden on folks getting started on Ubuntu Rust packaging.
Related issue
N/A
Checklist