View Single Post
Old 01-29-2012, 01:22 PM   #204
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Quote:
Originally Posted by ixtab View Post
@eureka: I probably didn't make this clear enough. The 46 MB is what would only be required on the computer which produces the (Kindle) locale bundles. The advantage of having everything there in this manner are
  • The hosting ("package-producing") computer doesn't need to have all locales installed
  • The package-producing doesn't need to worry about how to compile individual locales, or dependencies
  • The Kindle doesn't need to compile anything, where it's unsure whether dependencies are satisfied or not
  • The locale bundle (produced by the package-producing computer) would simply include the relevant locale .tgz for the Kindle to use.
No, you was clear enough. And almost all your points are provided by solution with source files:
  • Yes, The hosting ("package-producing") computer doesn't need to have all locales installed
  • Yes, The package-producing doesn't need to worry about how to compile individual locales, but package-producing program should know how to parse dependency tree and should add dependencies for specific locale code to package
  • But, The Kindle will need to compile something, but with certainly satisfied dependencies
  • Yes, The locale bundle (produced by the package-producing computer) would simply include the relevant locale input files and charmap for the localedef on Kindle to compile (and instead of cp command there will be localedef command)

Cons of source files solution: dependency tree should be computed (or pre-computed only once and then it will be stored in repo). Dependency tree is required but only for package-producing computer.

Pros of source files solution: Git repo will be smaller in size (9 additional MBs against 46 additional MBs)
eureka is offline   Reply With Quote