>>	see, will do.  do we really want to split base-runemodule-*?
>>	isn't it too fine-grained?
>Not sure.  My assumption is that most users won't be using more than one
>or two rune modules on a given system, and may want to trim a little
>(especially on ports such as the hpc ports, where space can be
>crucial...

/usr/lib/runemodule/libBIG5.a
/usr/lib/runemodule/libEUC.a
/usr/lib/runemodule/libEUCTW.a
/usr/lib/runemodule/libISO2022.a
/usr/lib/runemodule/libMSKanji.a
/usr/lib/runemodule/libUTF2.a
/usr/lib/runemodule/libUTF8.a

	here are items Asian people wants:

	- Japanese users will need ISO2022, MSKanji, and EUC.
	  some of them may probably want UTF8 too.
	- Korean users will want EUC.  some of them probably want UTF8 and
	  ISO2022 too.
	- Hongkong users will want BIG5.  not sure about UTF8.
	- Taiwanese users will want EUCTW and BIG5?.  not sure about UTF8.

	most of european people will be happy with singlebyte locales.

	they won't eat too much diskspace, so I'd say put all modules into
	one package.

itojun