Locale release procedures

[chansen]

Why is each locale released as a separate distribution when it has no dependencies besides Locale::CLDR and it's dependencies?

chansen

[ThePilgrim]

I split it up so you could just install the languages you wanted rather than having to download the whole lot.

There will be CPAN bundles for various regions released in the next couple of days. These should have gone up with the language data, but due to a combination of my upload script accidentally hammering the CPAN uploader and commitments over the weekend this got delayed.

If you look at the download size of version 0.25.4, the last released version to contain everything in one distribution you will see that the zipped size of the download was 4.17 Mega Bytes. I decided that that was getting stupidly large and would continue to grow as the number of languages and the coverage of each language grew. This seams to have been born out as the current size of just the base Locale::CLDR distribution is now over 1.2 Mega Bytes

[chansen]

Five or ten megabytes of locale data is nothing, my iPhone has more than ten megabytes of locale data!

What you have created is a nightmare for end users and vendor package managers, there is no way Locale::CLDR will be included in a vendor distribution. If I would like to develop a localized application, am I supposed to list all Locale::CLDR subclasses as a dependency?

The data could have been more compressed if you didn't ship each locale as a Perl module, and instead used a database like CDB or similar.

chansen

[kostyaten]

+1

[Anonymoosed]

It took me a while to realize what you had going, with all the confusion of the whole over spawned mess of separate distributions by language on cpan. The whole point of locale data is to grab the whole thing, install once, and use the data when need be, and focus on updating the dataset as it gets updated at unicode. Manually installing individual languages defeats this methodology.

Bundle::Locale::CLDR::World
Locale::CLDR::Transformations

It really would be better to have everything together in one package.

[ThePilgrim]

The way I devised it was to allow you to get all the data for the region you are interested in, so there is a bundle for North America and a separate one for the EU and so on. If you want everything then you get the everything bundle.