Custom module dependency handling

Here you can post about the issues related to modifications performed manually (not through the kiosk wizard). Example: swapped kernel, added 3rd party modules or files.
Please describe in detail what has been changed and hopefully other kiosk user will be able to help.
Porteus team wont resolve bugs posted in this category as we support only modifications made by the kiosk wizard.
Forum rules
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
chardho
White ninja
White ninja
Posts: 15
Joined: 12 Jan 2017, 05:39
Distribution: 4.7.0
Location: USA

Custom module dependency handling

Post#1 by chardho » 26 Oct 2018, 19:38

I'm trying to build a custom module following the #2 method shown in the tutorial linked below.
http://www.porteus.org/tutorials/9-modu ... udies.html

The missing link for me is how to get dependencies that are already installed in PKDE into the module. When running slacky -d it only shows dependencies that are missing for packages already installed on the system. Do I need to download each of the below dependencies individually and move them to the ~/temp/modwork folder and reinstall them there so that they are part of the new module?

I guess I'm still unclear on how the modules are created. Is it required to have all of the .txz packages for each dependency in the fakeroot folder to build the custom module?

chardho

alsa-lib>1.0.24
fftw
libsamplerate
ncurses
pciutils
psmisc
docbook-xsl (make)
systemd (make)
xmlto (make)

Locked