Author: Norman White Date: To: dyne3 Subject: [dyne:3] synaptic and .deb binary compatibility
-The up-to-date source code for Synaptic is at the debian website.
-While at the website I've tried the search "etch toolchain" and on
google -- inquirys of the same nature: I'm not getting any definitive
answers to my questions: (1) is *.deb's binary compatibility in its
implementation on its (modified?)kernelspace libraries? (2) or is it
just in the default userspace libraries?
-If it's in "1" then it would be presently beyond me to try to merge
dyne:bolic's system together with a "*.deb system".
-If it's in "2" then I should be able to build a chroot environment
from scratch to run Synaptic.
This chroot environment would run in a user's nest in its own
directory-- possibly a "/mnt/nest/.dynaptic" directory and be called
from a "dynaptic dynemodule". this would keep a nest's functionality
separate from .dynaptic's purpose and would allow a user, if needs-be,
to do a manual loop mount into an "at-boottime-unmounted nest" and
delete a 'nest filesystem' and copy in a new default nest filesystem
without affecting the /mnt/hdwhatever/partitionwhatever/.dynaptic
"subsystem".
I have done this so far with actual debian and debian-based systems
but I don't know if there will be a ticking .deb bomb waiting to
conflict with a dynebolic "plain vanilla kernel".