From Fedora Project Wiki
< Changes
(→Owner) |
No edit summary |
||
| Line 36: | Line 36: | ||
== Detailed Description == | == Detailed Description == | ||
During initial research of SIG about packaging we identified that inability to specify version range dependencies (<code>1.0 <= foo < 2.0</code>) in RPM is main blocker. This problem hits almost every other language ecosystem (esp. NodeJS), but it is not very noticable due to having not more than 2 versions. While packaging some applications we discovered need of having 3 or more versions of same crate.. | |||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Fedora will be one of first distributions (if not first) who package rust applications/libraries | * Fedora will be one of first distributions (if not first) who package rust applications/libraries | ||
* Packagers of other ecosystems/distributions will get ability to express version range dependencies and real example of its usage in various places | |||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
| Line 50: | Line 51: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/6889 #6889] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 84: | Line 85: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Install tool which is written in Rust and use it (list will be provided when change will be implemented). | |||
== User Experience == | == User Experience == | ||
* Packagers will be able to package Rust applications | * Packagers will be able to package Rust applications/libraries | ||
* Users will be able to install tools written in Rust from Fedora repositories (i.e. [https://github.com/BurntSushi/ripgrep ripgrep]) | * Users will be able to install tools written in Rust from Fedora repositories (i.e. [https://github.com/BurntSushi/ripgrep ripgrep]) | ||
* Packagers will be able to write dependency generators for RPM which returns rich dependencies (already implemented in RPM 4.14) | |||
== Dependencies == | == Dependencies == | ||
''Support for "with" rich-operator'' from [[Changes/RPM-4.14|RPM 4.14]] change is required to be implemented. | * ''Support for "with" rich-operator'' from [[Changes/RPM-4.14|RPM 4.14]] change is required to be implemented. | ||
* Release engineering tools needs to be adapted to use DNF (because YUM doesn't support rich dependencies) | |||
* FPC should allow ''at least'' <code>with</code> rich operator | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 116: | Line 120: | ||
--> | --> | ||
[[Category: | [[Category:ChangeReadyForWrangler]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Revision as of 12:34, 6 July 2017
Packaging Rust applications/libraries
Summary
Add required tools/instructions for packaging applications/libraries written in Rust.
Owner
- Name: Igor Gnatenko (on behalf of Rust SIG)
- Email: ignatenkobrain@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 27
- Last updated: 2017-07-06
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
During initial research of SIG about packaging we identified that inability to specify version range dependencies (1.0 <= foo < 2.0) in RPM is main blocker. This problem hits almost every other language ecosystem (esp. NodeJS), but it is not very noticable due to having not more than 2 versions. While packaging some applications we discovered need of having 3 or more versions of same crate..
Benefit to Fedora
- Fedora will be one of first distributions (if not first) who package rust applications/libraries
- Packagers of other ecosystems/distributions will get ability to express version range dependencies and real example of its usage in various places
Scope
- Proposal owners: Create tools for automatic conversion from crates.io to rpm's spec file, create RPM macro for generation of automatic dependencies, write packaging guidelines.
- Other developers: RPM developers to add support for expressing version range dependencies.
- Release engineering: #6889 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: Packaging Guidelines needs to be written for packaging Rust applications/libraries.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
Install tool which is written in Rust and use it (list will be provided when change will be implemented).
User Experience
- Packagers will be able to package Rust applications/libraries
- Users will be able to install tools written in Rust from Fedora repositories (i.e. ripgrep)
- Packagers will be able to write dependency generators for RPM which returns rich dependencies (already implemented in RPM 4.14)
Dependencies
- Support for "with" rich-operator from RPM 4.14 change is required to be implemented.
- Release engineering tools needs to be adapted to use DNF (because YUM doesn't support rich dependencies)
- FPC should allow at least
withrich operator
Contingency Plan
- Contingency mechanism: Move implementation to next release (once ready and if possible, backport to old release)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? ??
- Blocks product? -
Documentation
N/A (not a System Wide Change)