View Single Post
Old 06-29-2019, 09:12 AM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by x86 View Post
Thanks for your reply, NiLuJe.
I honestly do not know how to install binaries without a pms such as dpkg or apt-get. The only thing I came across when googling was something like
Code:
dpkg-deb -x <package.deb> <destination dir>
I can extract the git package, but cannot execute it because of mandatory dependency to libpcre++

I do not understand how to proceed. Should I merge all content from the mandatory depending .deb packages into a single folder where also my git* executable redides?
Start by understanding the basics of what a Debian package consists of:
https://www.madebymany.com/stories/w...debian-package
That particular post is 'sort of' mid-level information, there are more general purpose, low(est) level, utilities that can be used to "do it all by hand".
But no sense in getting too crazy when just starting the learning curve.

Now with the understanding of how a single (package) file can be de-composed into its constituent parts ...

You will need to decide how you are going to accomplish the desired result WITHOUT bricking the machine or having all of your work wiped by a surprise OTA experience.

There have been two general approaches posted here over the years (multiple, slightly differing, varieties of each posted here).

*) Build a full chrooted system (using space from the visible, USB storage area).
-) The downfall of that is a lot of duplication without even readonly access to the Kindle system.
But this type of example has been posted here multiple times over the years.

*) NOT build a fully chrooted system.
First question that often comes to mind is:
But wait, the Kindle system is ARM-Softfloat and anything within the past decade on Debian is ARM-hardfloat. How can that work without being one or the other?

Next learning curve:
All *nix-like (Unix like) systems can support MULTIPLE systems, concurrently.
It is only the default system that lives in the "system" directories, starting with /lib/libc. The kernel does not care what system it runs (since it makes only hardware and its own static software build).

Enter my one and only, worked example, of how to run more than a single system, concurrently.
Choice #2 has been a tad bit overly exotic for nearly everyone's taste here.
https://www.mobileread.com/forums/sh...d.php?t=240616
Hmm...
That thread is five years old this month, guess it wasn't such a grand idea after all.

Last edited by knc1; 06-29-2019 at 09:38 AM.
knc1 is offline   Reply With Quote