switch locale-gen to ARCHIVE=yes

<pitti> cjwatson: I think we can; it'll increase the time to build/remove locales, but that's rather insignificant
<pitti> cjwatson: I actually did some boot charts with locale-archive, but I didn't get any measurable difference
<cjwatson> locale build time is a bit of a concern on low-memory systems because localedef is so memory-hungry
<pitti> shoudl just be a matter of setting ARCHIVE=yes in /usr/sbin/locale-gen
<cjwatson> what sort of increase are we talking about? just running 'localedef --add-to-archive /usr/lib/locale/*' doesn't seem to take too long here
<pitti> and cleaning up the unarchived ones in postinst
<cjwatson> I was wondering if there were compatibility implications; I seem to recall the odd bug when the broken-out dirs were missing
<pitti> cjwatson: ah, good; removing a locale used to require rebuilding all other ones, but as I said that should not be a common use case
<pitti> cjwatson: I have that running in a VM for some days, but I didn't test it extensively; just standard desktop bits
<pitti> cjwatson: so perhaps we should switch it early in maverick for testing?
<cjwatson> --delete-from-archive seems to take negligible time
<pitti> cool
<pitti> seems that didn't exist back then (in belocs age)
<cjwatson> I suspect it doesn't make a huge boot difference because everything is LANG=C
<cjwatson> it's only once you reach a session that it starts making any difference at all
<pitti> the desktop bits do use the locale, though
<pitti> right
<pitti> and I didn't notice any difference there
<cjwatson> should we have *only* locale-archive, or the broken-out dirs as well?
<pitti> but still, it's fewer syscalls
<pitti> cjwatson: they do take a nontrivial amount of space, so I'd vote for either-or, not both
<pitti> Debian has used locale-archive only forever, I think
<pitti> (and Fedora, too)
<cjwatson> ok, if you're comfortable with either-or then I am too