Chrome, Truecrypt, compat32, wine and dependencies
Posted: 10 Jan 2012, 16:21
Hello everyone,
I just finished creating and testing my first set of modules. I elected to place small dependencies (less than 10% of the main program size) within the module itself in order to keep things simple for new users (I remember struggling with dependencies not too long ago). True to the Porteus spirit, each of these modules should run without any problem on a fresh Porteus 1.1 install simply by adding it to the modules folder or by adding it to the optional folder and then double clicking it after running Porteus. Only in the case of wine I kept the compat32 libraries in a separate module (but that should still be much easier to install than compiling the alien multilib libraries from scratch). Without further ado, you can find my modules at:
http://www.mediafire.com/?29l9t16ava2xv
I am not sure when this link will expire so I hope that one of you who maintains a proper repository will copy my files to it. The modules available are:
google-chrome-16.0.912.63-x86_64-1sl.xzm (30 mb) - includes all dependencies resolved through slackyd
truecrypt-7.0a-x86_64-1sl.xzm (8 mb) - includes all dependencies resolved through slackyd + sudo with a modification of /etc/sudoers allowing the guest user to sudo provided they know the root password
compat32-libraries-1.1.02_13.37-x86_64-1sl.xzm (48 mb)
wine-1.3.36-i486-1sg.xzm (16 mb) - depends on compat32-libraries
winetricks-20110614-i686-1sl.xzm (124 kb) - depends on wine
For any of you who are curious, here is my step-by-step process of creating these modules after booting Porteus in Always Fresh mode with all non-base modules disabled (by moving them to the optional folder or using noload=module_name at the boot screen):
In the case of Truecrypt, I only discovered that sudo was required after running it so I downloaded it, installed it to the /var/slackyd/tmp folder, and modified /etc/sudoers before running the dir2xzm command. wine and winetricks were not available in slackyd but they were easy enough to find as .txz files and convert to .xzm, after which I ran slackyd to discover that the compat32-libraries dependency was missing.
Porteus gurus, please let me know if you have any feedback or suggestions regarding my approach. For the rest of you, I hope this helps!
Maverick
I just finished creating and testing my first set of modules. I elected to place small dependencies (less than 10% of the main program size) within the module itself in order to keep things simple for new users (I remember struggling with dependencies not too long ago). True to the Porteus spirit, each of these modules should run without any problem on a fresh Porteus 1.1 install simply by adding it to the modules folder or by adding it to the optional folder and then double clicking it after running Porteus. Only in the case of wine I kept the compat32 libraries in a separate module (but that should still be much easier to install than compiling the alien multilib libraries from scratch). Without further ado, you can find my modules at:
http://www.mediafire.com/?29l9t16ava2xv
I am not sure when this link will expire so I hope that one of you who maintains a proper repository will copy my files to it. The modules available are:
google-chrome-16.0.912.63-x86_64-1sl.xzm (30 mb) - includes all dependencies resolved through slackyd
truecrypt-7.0a-x86_64-1sl.xzm (8 mb) - includes all dependencies resolved through slackyd + sudo with a modification of /etc/sudoers allowing the guest user to sudo provided they know the root password
compat32-libraries-1.1.02_13.37-x86_64-1sl.xzm (48 mb)
wine-1.3.36-i486-1sg.xzm (16 mb) - depends on compat32-libraries
winetricks-20110614-i686-1sl.xzm (124 kb) - depends on wine
For any of you who are curious, here is my step-by-step process of creating these modules after booting Porteus in Always Fresh mode with all non-base modules disabled (by moving them to the optional folder or using noload=module_name at the boot screen):
Code: Select all
su # then enter root password
slackyd -u
cd /var/slackyd
rm -R tmp/
rm *.txz
pkgname=my_package_name # change this to the name of the package you are looking for such as 'chrome' or 'truecrypt'
slackyd -g $pkgname
installpkg --root tmp/ *.txz
dir2xzm tmp/ $pkgname.xzm
mv $pkgname.xzm /mnt/sdb1/porteus/optional/ # change this to wherever your porteus files are located
Porteus gurus, please let me know if you have any feedback or suggestions regarding my approach. For the rest of you, I hope this helps!
Maverick