Quote:
Originally Posted by george.talusan
Lot of noise here about nothing.
|
George, let me point out something obvious.
If anyone, here, at this site had known for sure that the source code to the latest release of the KoboGlo or Aura, was in that upper directory -- they would have pointed out where it was, or made fun of me for not looking.
The very fact that a thread has to go this far before we can even guess where the right source code is -- shows there is a problem.
Quote:
|
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.
|
Yes, there is a trust issue for an obvious reason; I already downloaded a two year old archive that wasn't labeled as archive only; and didn't realize it was the wrong one until I compiled the code and checked the version numbers and noticed it was wrong. There's nothing which says which archive is up to date for the Glo or Aura; and your comment was merely "you could look" ... it wasn't "the most recent code for busybox is here"
There's a saying -- once burnt, twice shy. Well ... I've been burnt more than twice with Kobo support.
In the new Busybox directory that I did find, there is a ALSO a note saying "of course you can always download the latest source from ..."; which is a generic pointer to the busybox respository for the developers of Busybox. So it was not possible for me to tell if the latest version of busybox used on the Aura or Glo, was even in the git-hub repository, or if the git hub version was only there because you had patched that particular version historically. There's no documentation of the reason for a particular directory existing or not existing or whether I should use a newer version from busybox, with an old configuration file from your archive -- or what.
Most companies working with source code document at least a tiny bit better, for example:
If you go to
packages.slackware.com, they use a system that has older releases, slackware 12, 13, 13.1, etc. and a separate directory labeled "current"; which at least gives the user a clue between historical archives, and present day working directory.
It's pretty counter-intuitive to look at an archive which is two years old and go -- oh yeah, that must be the one he used for the release that came out last month; unless there is a note of some kind.
Quote:
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.
|
I have no intention of building a change root.
I intend on fixing the code that the Aura uses natively.
Of course, I will post to git hub as I see problems in the future; and hopefully you won't close the thread so quickly that I can't fully ask the question? I mean, if I have a problem -- and no-one else, here could answer it -- then it's clear that many people have a problem knowing how to compile your archives; and you'll just end up answering the same question multiple times if you cut the answer short -- with unhappy customers.
I can't read minds, and I know that you know how you did it, and why -- and I'm sure it's all very reasonable in your own mind; but the rest of us are guessing.
I want to continue posting the results, here -- or, at least links to the Github comments, for since you don't have individual archives for all the different readers, it seems that posting the successful recompilation steps for the Arua and Glo will aid the public in general.
It would be also be bad to leave this thread hanging as if the problems were never resolved.
People doing searches often find threads like these, hoping for solutions.
As a note, I figured out a way to disable the kobo accessing the store while still allowing it to remain logged in, eg: with an app. I wrote, so at least my son (who's birthday was yesterday), got to use the Kobo Reader for the first time -- for he can now read books that I have bought for him, without my having to worry about my credit card being charged for purchases I didn't authorize should the logged in reader get lost or stolen --so; there's no risk of chargebacks to Kobo over unauthorized purchases.
That should make us both happy, as open source benefits us both in reducing paperwork.
Cheers.