Various notes for taking a package from some other Linux distribution and turning it into a Slax-compatible module.
- Official packaging for Slax to provide the information and data to the Slax team for official inclusion to their repository.
Packaging compiled programs for Slax for turning compile-able source into a Slax .sb module.
Two success stories:
THESE ARE RANDOM NOTES
Convert a Slackware .txz to a Slax .sb module ∞
TODO - There's another Slackware package type/extension. I haven't researched the process for anything else.
http://old.slax.org/forum.php?action=view&parentID=52222 had good luck getting things working.
I think txz2sb is preinstalled
\wget -c http://www.slackers.it/repository/ecryptfs-utils/ecryptfs-utils-106-x86_64-1cf.txz \wget -c ftp://ftp.linux.cz/pub/linux/slackware/slackware64-14.0/slackware64/l/keyutils-1.5.5-x86_64-1.txz \txz2sb ecryptfs-utils-106-x86_64-1cf.txz \txz2sb keyutils-1.5.5-x86_64-1.txz
... then move stuff into somewhere, and reboot?
slax activate modulename
test ecryptfs using https://github.com/spiralofhope/shell-random/blob/master/live/eCryptfs-mount.sh
Convert a Debian .deb to a Slax .sb module ∞
Semi-tested.. had some error message regarding libecryptfs.so.0 I believe.
find /usr/lib/ -name libecryptfs.so*
cd /usr/lib/ ln -s libecryptfs.so.1 libecryptfs.so.0
Convert an .rpm to a Slax .sb module ∞
I don't know what version/type of "RPM" this idea refers to.
This might be possible. Information unknown.
dealing with dependencies? ∞
.. but for all of these, what about dependency resolution? Am I really supposed to figure out the dependencies and build them into packages? And each dependency's dependency too?