View Single Post
Old 06-09-2015, 08:15 PM   #26
george.talusan
Kobo Developer Intern
george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.george.talusan ought to be getting tired of karma fortunes by now.
 
george.talusan's Avatar
 
Posts: 84
Karma: 253043
Join Date: Apr 2010
Location: Toronto, ON
Device: Kobo Touch, Kobo Mini, Kobo Glo
Lot of noise here about nothing.

The git repositories that are hosted on github are kept up-to-date. Just because you see that something hasn't been updated since 2013 or whatever doesn't mean it isn't the latest. It is in fact the latest.

The problem that I see here is that there's a request for source code, the request is fulfilled, then there is a trust issue regarding whether or not this source code is the latest.

If the build instructions are followed from the Kobo-Reader repository using the individual git repos, you should be able to build up your own chroot. The main reason for the big split is because github doesn't allow binaries greater than 100MB and it's easier to just track upstream repositories if we use git as intended.

In other words, just clone and compile.

UPDATE: Also if there's anything missing, then file an issue on github instead of complaining here.

Last edited by george.talusan; 06-09-2015 at 08:49 PM.
george.talusan is offline   Reply With Quote