From Fedora Project Wiki
m
(clarify scope)
Line 65: Line 65:
  
 
== Scope ==
 
== Scope ==
* Proposal owners: Check all langpacks providing packages (like fonts, input-methods) add Supplements tag in their SPEC file and build them.  We will track the progress of this Change in [https://copr.fedorainfracloud.org/coprs/pnemade/langpacks/ Langpacks Copr] project.
+
* Proposal owners:
 +
** Move comps language groups packages into rich weak dependencies in langpacks package.
 +
** Test each langpacks package can pull in the fonts and input-methods as required for that language
 +
** Initial development of this Change will be testable from this [https://copr.fedorainfracloud.org/coprs/pnemade/langpacks/ Langpacks Copr] project.
 +
** Removal all language support groups from comps-f30.xml.in via a pull request.
 
<!-- 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: To all other developers of packages who provides langpacks, they need to add the Supplements tag as given in this [https://fedoraproject.org/wiki/Packaging:Langpacks Langpacks guideline] to each langpack subpackage.
+
* Other developers: can help provide langpacks support if needed by adding a Supplements tag as given in this [https://fedoraproject.org/wiki/Packaging:Langpacks Langpacks 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?-->
  

Revision as of 07:08, 10 January 2019


Replace Comps Language Group With Langpacks

Summary

Language support groups in Comps file will get replaced by weak rich dependencies in the langpacks package.

With this Change meta-packages like langpacks-ja will also install required fonts and input-methods for the given language.

Owner

  • Release notes owner:

Current status

  • Targeted release: Fedora 30
  • Last updated: 09-Jan-2019
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Note.png
This change will remove the need of having the language specific comps groups in Fedora

langpacks-* meta-packages have been in Fedora since F24. Currently they only install locales, translation langpacks, and dictionaries, but not fonts or input-methods, etc. With this Change they will install required fonts and input-methods for a language as well.

e.g. When you do a net-install of Fedora in Japanese then with langpacks-ja the installation of any base package like libreoffice-core or man-pages causes libreoffice-langpack-ja or man-pages-ja to be installed. After this change using weak dependencies like Supplements in langpacks, Japanese fonts and input-method can also get installed if appropriate.

Then there is no need for language comps groups to exist: they will be handled by the langpacks package.

See https://pagure.io/i18n/issue/97 for more background discussion.

Benefit to Fedora

Users can install complete language support now using langpacks only. This will also help to remove the long deprecated language support groups from comps.

Scope

  • Proposal owners:
    • Move comps language groups packages into rich weak dependencies in langpacks package.
    • Test each langpacks package can pull in the fonts and input-methods as required for that language
    • Initial development of this Change will be testable from this Langpacks Copr project.
    • Removal all language support groups from comps-f30.xml.in via a pull request.
  • Other developers: can help provide langpacks support if needed by adding a Supplements tag as given in this Langpacks guideline to each langpack subpackage.
  • Release engineering: none
  • Policies and guidelines: none

Upgrade/compatibility impact

None.

How To Test

User Experience

Currently users can get complete language support installed only using "dnf group install <language>-support" command. After this Change gets implemented end users can get their language support installed using the meta-package "langpacks-<langcode>".

Dependencies

No Other Change depend on this.

Contingency Plan

  • Contingency mechanism: If this change is not completed by final development freeze then we need to target this for F31. We are just proposing to add additional information in langpacks packages that is Supplements tag. This should not affect individual langpacks packages installation by dnf.
  • Contingency deadline: I don't think we will need anything to revert or apply any contingency plan here if this is not completed by beta freeze.
  • Blocks release? No
  • Blocks product? N/A

Documentation

  • Need to add about this in the Release notes

Release Notes