Bug 512663 (langpack-support) - Review Request: langpack-support - Meta packages for Yum langpack support
Summary: Review Request: langpack-support - Meta packages for Yum langpack support
Keywords:
Status: CLOSED NOTABUG
Alias: langpack-support
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-20 09:01 UTC by Jens Petersen
Modified: 2009-11-24 06:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-16 01:13:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jens Petersen 2009-07-20 09:01:58 UTC 
Spec URL: http://petersen.fedorapeople.org/langpack-support/langpack-support.spec
SRPM URL: http://petersen.fedorapeople.org/langpack-support/langpack-support-0.0-1.fc11.src.rpm
Description: 
See https://fedoraproject.org/wiki/Features/YumLangpackPlugin

The package should provide the langpack meta packages for each language
with langpacks in Fedora.  There will be a separate package review 
for the yum plugin itself soon which I will link to this bug.
Comment 1 Bill Nottingham 2009-07-20 14:52:34 UTC 
Why not build by parsing iso-codes? (Woo, automation!)
Comment 2 Jens Petersen 2009-07-21 03:09:59 UTC 
It did cross my mind for the language names at least.
Comment 3 Jens Petersen 2009-07-21 04:09:34 UTC 
(In reply to comment #1)
> Why not build by parsing iso-codes? (Woo, automation!)  

But seriously so you have a "sketch" or example of how to do it?
I am not really sure but if we avoid the package name it might
be possible?
Comment 4 Jens Petersen 2009-11-16 01:13:25 UTC 
I think I will close this for now since it is no longer needed
by yum-langpacks.
Comment 5 Jens Petersen 2009-11-24 06:02:28 UTC 
(See bug 536737 for yum-langpacks.)
Note You need to log in before you can comment on or make changes to this bug.