Re: Changes to rpmstrate (or localedrake?) for zh_TW

pablo-4qZELD6FgxhWk0Htik3J/[email protected] writes:

> Kaixo!
>
> On Mon, Feb 12, 2007 at 02:13:46PM +0100, Pixel wrote:
>
>> > So the behaviour should be changed to:
>> >
>> > * for each requested language do:
>> > 	* look at its LANGUAGE variable, and install packages for
>> > 	  the first matching locale (it may be different locales for
>> > 	  different packages)
>> 
>> currently it's not done that way at all, since it can't work for
>> mozilla-firefox-*. we do:
>> 
>> for each package do:
>>    * if it requires locales-xxx, select it iff that locales is
>>    selected
>
> A possible solution could maybe be to split locales packages
> for some languages (zh_CN/zh_TW, pt_BR/pt, nn/nb);
> however, as the list of installed locales is computed from the LANGUAGE
> variable, there should be a special rule to not install the other
> locales-* variant (maybe it could be chosen during install,
> eg: "Install all language variants (uses more disk space)? (Y/n)"
>
>> we'll have to change one day, so that rpmsrate format can be
>> simplified and get rid of clean-rpmsrate. for this, virtual provides
>> must be added, even for things like mozilla-firefox-* which do not
>> have a main package, only l10n packages (kde-i18n-*, koffice-i18n-*,
>> koffice-l10n-* already have a provide)
>
> You mean something like "Provides: l10n-zh_CN"
> and request all packages with such a provides to know what is
> installable for that locale?

no. i mean something like "Provides: mozilla-firefox-l10n"

we'll get what Funda Wang suggests, except for Suggest vs Requires.
Here is what i wrote in the same mail in may 2006:

> Many packages work with no l10n package
> installed (eg: mozilla-firefox). One solution would to
>   - create an empty mozilla-firefox-en package (alike kde-l10n-en), 
>   - make mozilla-firefox-LANG provide mozilla-firefox-l10n 
>   - make mozilla-firefox require mozilla-firefox-l10n
> This can be more nicely handled use suggest:
>   - make mozilla-firefox-LANG provide mozilla-firefox-l10n 
>   - make mozilla-firefox suggest mozilla-firefox-l10n

but urpmi doesn't handle Suggests and treat them as Requires.

in any case, even if mozilla-firefox doesn't Requires/Suggest
mozilla-firefox, we can have the other way round working nicely *now*,
using "urpmi mozilla-firefox-l10n". This is what i think is the best
evolution from current rpmsrate dead-end