Dynebolic & Software packages

Overview You can install software using a variety of pre-made packages into a dyne:bolic system. Unless the package installs them to a nest they are lost at reboot/shutdown & have to be installed again at nest startup. The example we will use is a program called spaghetti in homage to Jaromil's wonderful cooking.

Supported Formats Dyne:bolic has three formats installed: these are Debian packages (spaghetti.deb), Red Hat packages (spaghetti.rpm) and Slackware packages (spaghetti.tgz). Although these formats are names after their originating distro they are used across multiple distros. Jaromil has stated that in the future he intends to add support for autopackage.

rpm & deb packages At the time of writing (using 2.4.2) both these methods seem to fail. If you have had success with either please consider revising this entry. In the meantime you can convert rmp's or deb packages to Slackware packages using a terminal with the command:

alien -t spaghetti.deb (obviously substituting your packagename for spaghetti.deb).

This needs to be done in a writable directory such as your nest. You can then use your Slackware package as detailed below.

Slackware packages You install Slackware packages using a terminal with the command

installpkg spaghetti.tgz (obviously substituting your packagename for spaghetti.tgz).

You can browse inside slackeare packages using midnight commander (found under the file menu in the menuing system or by typing mc at a terminal). Use it to find where the main program file is: usually they are somewhere in /usr or /usr/local though they have been spotted in the wild in /opt. You then run the program by typing the full path to it

/usr/bin/spaghetti