From Fedora Project Wiki
No edit summary
 
(14 intermediate revisions by 2 users not shown)
Line 9: Line 9:


== Current status ==
== Current status ==
* Targeted release: [[Releases/12| Fedora 12]]  
* Targeted release: [[Releases/??| ??]]  
* Last updated: 2009-07-24
* Last updated: 2010-04-07
* Percentage of completion: 30%
* Percentage of completion: 100%


== Detailed Description ==
== Detailed Description ==
Line 22: Line 22:
Here is an outline of the design and current assumptions:
Here is an outline of the design and current assumptions:


# add langpack-support-<lang> metapackage for each language, which users can install if they want langpack support for the language
# install plugin (langpack language defaults to current locale)
# the langpack metapackages will all require yum-plugin-langpacks
# langpack-support-<lang> metapackages will be added to the comps lang support groups
# when user activates yum (eg through PackageKit) the plugin will check if langpacks are needed or available for the packages involved in the transaction
# when user activates yum (eg through PackageKit) the plugin will check if langpacks are needed or available for the packages involved in the transaction
# maybe keep conditional lang entries for now in F12 and drop them later in F13 say
# keep conditional lang support entries in comps for now and maybe drop them in a later release
# package languages can be configured in .conf file


Optional/longer term ideas (likely deferred for later).
Optional/longer term ideas (deferred for later).
# allow for whitelisting/blacklisting of specific langpacks
# allow for whitelisting/blacklisting of specific langpacks
# setting for which langs appear by default in gdm lang top menu ([https://bugzilla.redhat.com/show_bug.cgi?id=505484 rfe bug])
# setting for which langs appear by default in gdm lang top menu ([https://bugzilla.redhat.com/show_bug.cgi?id=505484 rfe bug])
# recommendation for Packaging Guideline for standard naming of langpacks (eg <basename>-langpack-<lang>)
# recommendation for Packaging Guideline for standard naming of langpacks (eg <basename>-langpack-<lang>)
# (longterm) extend to handling gettext translation .mo files
# (longterm) extend to handling gettext translation .mo files
=== anaconda ===
Anaconda will need to require yum-plugin-langpacks and enable it by default (as outlined in the above mail).
Additionally the plugin must be able to take into account new langpack-support metapackages being added in an rpm transaction when determining langpacks (not just currently installed langpack-support metapackages).
=== pungi ===
For pungi, since all the langpack-support metapackages will be listed in comps if it also requires and enables yum-plugin-langpacks it should be able to pull in the corresponding langpacks needed to compose Fedora trees, etc.
=== livecd-tools ===
livecd-tools probably also needs to require yum-plugin-langpacks and enable it.  Currently the official Live Spins don't actually include any @lang-support groups. Localized spins should list any required langpack-support-<lang> meta package or @<lang>-support group anyway in their kickstart file.
=== comps ===
Once the feature is available in Rawhide all the metapackages will be added to the respective language support groups in comps.
=== yum ===
Rather than making changes to each of the tools using Yum (as outlined above) it might be easier just to enable the langpack plugin in yum by default to avoid having to change Yum code in multiple places?


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 55: Line 37:


== Scope ==
== Scope ==
# Write yum plugin, test, wash, rinse, repeat
# Complete initial yum plugin and package [done]
# Add yum-plugin-langpacks package to fedora or yum-utils upstream
# Add yum-plugin-langpacks package to fedora [done]
# Add metapackages package to fedora: see [https://bugzilla.redhat.com/show_bug.cgi?id=langpack-support pkgreview]
# Include in comps [done: added to @base]
# Include in comps
# Fedora QA Test Day in Feb [done]
# Tweaks, improvements, bugfixes [done]


== Test Plan ==
== Test Plan ==
Test various scenarios
Test various scenarios
# Do a Japanese Fedora install, and then later add kde and eclipse
* Do a Japanese Fedora install, and then later add kde and eclipse
# Do English Fedora install and groupinstall some lang support and add openoffice
* Do English Fedora install and groupinstall some lang support and add openoffice
# etc
 
The effect of yum-langpacks in @base needs testing with:
* anaconda
* pungi
* livecd-tools


== User Experience ==
== User Experience ==
# Installation of langpacks will Just Work.
Installation of langpacks will Just Work.


== Dependencies ==
== Dependencies ==
Line 73: Line 60:


== Contingency Plan ==
== Contingency Plan ==
Keep langpacks listed in comps as conditional packages in addition to the new metapackages, or just revert.
Make yum-langpacks package optional in @base


== Documentation ==
== Documentation ==
none yet
* Mentioned in the [[Documentation_I18n_Beat]]
 
== Release Notes ==
* to be documented in the I18n docsbeat
* '''FIXME''': Please add text here or link to I18n docsbeat


[[Category:FeatureAcceptedF12]]
[[Category:FeaturePageIncomplete]]

Latest revision as of 11:14, 7 April 2010

Yum Langpack Plugin

Summary

A yum plugin that allows langpacks to be automatically installed for your native language when base packages with langpacks get installed.

Owner

Current status

  • Targeted release:  ??
  • Last updated: 2010-04-07
  • Percentage of completion: 100%

Detailed Description

Currently when users install packages with langpacks they have to install the langpacks themselves by hand (if they even know about them).

Last year in a related thread on fedora-devel-list Bill Nottingham posted an initial proof of concept of this plugin. This feature will polish that further and make it ready for general use. (See also this rfe bug.)

This feature will also allow firefox and thunderbird to earn langpacks as they deserve.

Here is an outline of the design and current assumptions:

  1. install plugin (langpack language defaults to current locale)
  2. when user activates yum (eg through PackageKit) the plugin will check if langpacks are needed or available for the packages involved in the transaction
  3. keep conditional lang support entries in comps for now and maybe drop them in a later release
  4. package languages can be configured in .conf file

Optional/longer term ideas (deferred for later).

  1. allow for whitelisting/blacklisting of specific langpacks
  2. setting for which langs appear by default in gdm lang top menu (rfe bug)
  3. recommendation for Packaging Guideline for standard naming of langpacks (eg <basename>-langpack-<lang>)
  4. (longterm) extend to handling gettext translation .mo files

Benefit to Fedora

Users will get langpacks for their language installed automatically if they wish.

Scope

  1. Complete initial yum plugin and package [done]
  2. Add yum-plugin-langpacks package to fedora [done]
  3. Include in comps [done: added to @base]
  4. Fedora QA Test Day in Feb [done]
  5. Tweaks, improvements, bugfixes [done]

Test Plan

Test various scenarios

  • Do a Japanese Fedora install, and then later add kde and eclipse
  • Do English Fedora install and groupinstall some lang support and add openoffice

The effect of yum-langpacks in @base needs testing with:

  • anaconda
  • pungi
  • livecd-tools

User Experience

Installation of langpacks will Just Work.

Dependencies

None

Contingency Plan

Make yum-langpacks package optional in @base

Documentation

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/YumLangpackPlugin&oldid=164438"