From Fedora Project Wiki
(User Experience)
(How To Test)
Line 78: Line 78:
== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
* [[QA:Langpack Dnf Application]]
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
N/A (not a System Wide Change)
== User Experience ==
== User Experience ==

Revision as of 05:35, 25 December 2014

Dnf Langpack Plugin


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


  • Name: Parag Nemade
  • Email: pnemade at fedoraproject dot org
  • Release notes owner:

Current status

  • Targeted release: Fedora 22
  • Last updated: 2014-12-12
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

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

This is similar to what we have yum langpacks plugin which is already a Features/YumLangpackPlugin in Fedora.

Benefit to Fedora

Users will get langpacks for their language installed automatically if they wish. They can also use langinstall command to install any other language translations.


  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

User Experience

User will get langpacks installed automatically when a base package gets installed. User can also install or remove any other language translations.


No Other Change depend on this.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) 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


Release Notes