(→Scope) |
|||
| Line 63: | Line 63: | ||
== Scope == | == Scope == | ||
* Proposal owners: Check all langpacks providing packages add Supplements tag in their each langpack subpackage. | * Proposal owners: Check all langpacks providing packages add Supplements tag in their each langpack subpackage. Create metapackages like langpacks-<langcode>. | ||
<!-- What work do the feature owners 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 the feature owners 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?--> | ||
* Other developers: N/A (not a System Wide Change) | * Other developers: N/A (not a System Wide Change) To all other developers of packages who provides langpacks, they need to add the Supplements tag as given in this [https://fedoraproject.org/wiki/PackagingDrafts/Langpack draft guideline] to each langpack subpackage. | ||
<!-- 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: N/A | * Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
* Policies and guidelines: | * Policies and guidelines: Working with FPC on this new [https://fedoraproject.org/wiki/PackagingDrafts/Langpack langpacks guideline] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 06:46, 25 January 2016
Langpacks Using RPM Tags
Summary
Langpacks installations is re-designed using RPM weak and rich dependencies.
Owner
- Name: Parag Nemade
- Email: pnemade at fedoraproject dot org
- Name: Jan Silhan
- Email: jsilhan at fedoraproject dot org
- Release notes owner:
Current status
- Targeted release: Fedora 24
- Last updated: 22-Jan-2016
- Tracker bug: []
Detailed Description
This is similar to what we have dnf langpacks plugin which is already in Fedora but there is one missing thing that this plugin currently does not provide automatic installation of langpacks. E.g. if you enable or install Fedora in Japanese language then installation of any base package like libreoffice-core or man-pages are not installing automatically libreoffice-langpack-ja or man-pages-ja. This is because dnf is not providing required hook to re-resolve the transaction unlike yum. But now with using RPM tags or weak dependencies like Supplements, we just need to ensure we have langpacks-xx metapackage is already installed on the system and when a base package is getting installed, it will pull its langpack for that xx language automatically in the transaction set.
This will help in anaconda installation also. When particular set of languages are selected in anaconda then anaconda should pull all the required langpacks in the same initial installation.
Benefit to Fedora
Users will get langpacks for the given language installed. This Change provides language metapackages which user need to just install and they will get all available langpacks for which base package is already installed on the system.
Scope
- Proposal owners: Check all langpacks providing packages add Supplements tag in their each langpack subpackage. Create metapackages like langpacks-<langcode>.
- Other developers: N/A (not a System Wide Change) To all other developers of packages who provides langpacks, they need to add the Supplements tag as given in this draft guideline to each langpack subpackage.
- Release engineering: N/A
- Policies and guidelines: Working with FPC on this new langpacks guideline
Upgrade/compatibility impact
None.
How To Test
User Experience
With single commands users can install or remove langpacks for requested languages.
Dependencies
No Other Change depend on this.
Contingency Plan
- Contingency mechanism: N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
- Need to add about this in the Documentation_I18n_Beat