[SOLVED] Module creation - /var/log/scripts issue (?)
Posted: 24 Feb 2011, 19:48
I'm getting some strange behavior with a module that I'm trying to build, and I'm not sure if this is a bug or if there's something I'm leaving out of the module building process... I kind of think I'm neglecting something, so that's why I'm posting my question here instead of bug reports.
This issue is repeated in Porteus 09 64-bit and V1 alpha (both 32 and 64 versions)--haven't tested on v09 32 bit.
I am trying to build a module for GIMP. My process was to:
1. update slackyd (slackyd -u)
2. check for missing packages in the base system (slackyd -d)
3. download the gimp txz package (slackyd -g gimp)
4. convert gimp package to porteus module and activate it
5. check missing packages again (slackyd -d), and download packages that were added to the list since step no. 2
6. convert all dependencies (all libraries) to modules
7. activate all modules to test. Gimp worked successfully.
8. use porteus-module-tools to merge all modules together, to gimp-alldep.xzm
This module (gimp-alldep.xzm) will run gimp successfully if placed in /porteus/modules and injected at startup. If I leave it in /porteus/optional and activate it after startup, however, it gives me a missing dependency error. When I extract the module, I see that all of the required drivers are in place. And, they even show up in my live filesystem when I activate the module. But what is missing are links. Each of the original modules contained an install script, that gets placed in the module at /var/log/scripts. For example, the package aalib-1.4rc5-x86_64-3 puts in the following script:
The links are properly installed if I have my "all deps" module in /porteus/modules, or if I do not merge the modules and activate them individually. The individual scripts do exist inside my merged module, so I'm clueless as to why this is occurring.
I'm looking forward to an "official module" HOWTO once we have a package manager
Thanks!
Posted after 2 hours 1 minute 26 seconds:
Should I be using installpkg -root /tmp/gimp on all of the txz's, and then dir2xzm? maybe that would create the links inside the module.
This issue is repeated in Porteus 09 64-bit and V1 alpha (both 32 and 64 versions)--haven't tested on v09 32 bit.
I am trying to build a module for GIMP. My process was to:
1. update slackyd (slackyd -u)
2. check for missing packages in the base system (slackyd -d)
3. download the gimp txz package (slackyd -g gimp)
4. convert gimp package to porteus module and activate it
5. check missing packages again (slackyd -d), and download packages that were added to the list since step no. 2
6. convert all dependencies (all libraries) to modules
7. activate all modules to test. Gimp worked successfully.
8. use porteus-module-tools to merge all modules together, to gimp-alldep.xzm
This module (gimp-alldep.xzm) will run gimp successfully if placed in /porteus/modules and injected at startup. If I leave it in /porteus/optional and activate it after startup, however, it gives me a missing dependency error. When I extract the module, I see that all of the required drivers are in place. And, they even show up in my live filesystem when I activate the module. But what is missing are links. Each of the original modules contained an install script, that gets placed in the module at /var/log/scripts. For example, the package aalib-1.4rc5-x86_64-3 puts in the following script:
Code: Select all
( cd usr/lib64 ; rm -rf libaa.so.1 )
( cd usr/lib64 ; ln -sf libaa.so.1.0.4 libaa.so.1 )
( cd usr/lib64 ; rm -rf libaa.so )
( cd usr/lib64 ; ln -sf libaa.so.1.0.4 libaa.so )
I'm looking forward to an "official module" HOWTO once we have a package manager
Thanks!
Posted after 2 hours 1 minute 26 seconds:
Should I be using installpkg -root /tmp/gimp on all of the txz's, and then dir2xzm? maybe that would create the links inside the module.