Install+Use SlackW 14.1 dev apps via CD-boot, USB

[itfactor36]

Am a n00B to Porteus, but not at all to Linux or Slackware http://www.slackware.com/
Have a complicated question (at least for me ) regarding using one of the latest Porteus 5.x on three computers:

1. This desktop tower x86_64 PC running Slackware 14.2 using the XFCE desktop environment (DE) -- also has the Fluxbox Window Manager.
2. A memory-constrained laptop PC with a flaky DVD-drive running x86_64 Debian GNU/Linux Stable using the LXQt DE - also has the LX DE.
3. An older 2007-model, memory-constrained, dual-core 64bit Apple iMac upgraded to Mac OS X 10.6.x Snow Leopard with its own unique DE https://www.apple.com/newsroom/2009/08/ ... August-28/
   
   Wish to run Porteus from a CD as opposed to a DVD or USB becuz ...
   • both liveDVDs and bootable liveUSBs bootup way too slowly on machines b. and c.
   • an iMac-compatible-formatted USB drive can be used to transfer files between both b. and c. and the same USB drive can be ideally suited to store and use Porteus's /porteus save folder for the iMac machine c., booted off the Porteus liveCD
   Given the availability of this machine a. having a fully-functional Slackware 14.2 installed, How could one install and use as many as are necessary of the SlackBuild 14.1 SBo development apps built from https://slackbuilds.org/repository/14.1/development/ on machine a. for using Porteus 5.x from the above USB drive on the CD-booted iMac machine c. ??
   
   All three computers a., b., and c. can successfully CD-boot from most of the 64bit Porteus DE versions listed at <mirror-name>/porteus/x86_64/Porteus-v5.0/ as well as super slowly from an older KNOPPIX 7.2 liveCD <mirror-name>/KNOPPIX_V7.2.0CD-2013-06-16-EN.iso on the latter two machines b. and c. :|
   
   to those who can best help out here or at least point this Slackware user in the right direction

[ncmprhnsbl]

welcome to porteus forums
do i have this right?: you're asking about using packages built for/on slackware14.2 from 14.1 slackbuilds on porteus 5.0 (rc1)?
main thing to note: porteus 5.0 (rc1) was built using slackware current (as of june 2019) packages so there may be compatibility issues.
also since porteus is very much stripped down compared with a standard slackware install, missing deps could also be an issue.
on the positive side: it's quite easy and safe to find out, since porteus has some handy tools for handling packages.
in particular, running live, using a filemanager, select your package(s), rightclick, and in the menu is the option to install the package (to the live system) ..you can then attempt to run it, and investigate why it doesn't, if that's the case(using terminal,strace,ldd .. etc) and because of the transient nature of the live system, there's no danger of breaking anything..
there's quite a lot more: bundling packages/configs into modules, remastering the cd and so on..

EDIT: also: porteus 4.0 is based on 14.2, so would be more likely to work with your packages..

[Ed_P]

EDIT: also: porteus 4.0 is based on 14.2, so would be more likely to work with your packages..

Really! I thought it was based on 14.1. This is what I see if it's any help.

Code: Select all

Boot mode:     ISO /ISOs/Porteus-CINNAMON-v4.0-x86_64.iso
OS:       Porteus-v4.0
ARCH:     x86_64
Kernel:   Linux porteus 4.16.3-porteus
Desktop:  jinnamon-180702.xzm  Cinnamon 3.8.6

[ncmprhnsbl]

I thought it was based on 14.1

Code: Select all

cat /etc/slackware-version
Slackware 14.2+

actually though: from Porteus-v4.0 is released!
"Core is based on Slackware current"
at least what current was as per april 2018, which was a lot closer to 14.2 than current of now..

[Ed_P]

Code: Select all

cat /etc/slackware-version
Slackware 14.2+

Thank you ncmp. I need to update my boot scripts.

[itfactor36]

Tnakis for the fast feedback!

EDIT: also: porteus 4.0 is based on 14.2, so would be more likely to work with your packages..

On a positive note, have no problem downloading and using the appropriate versions of Porteus 4.0, as am unlikely to update Slackware 14.2 x86_64 to Slackware current for the same arch in the near future. And definitely haven't heard news in http://www.slackware.com/ to the effect that Patrick and the rest of his Slackware team are just about ready to release Slackware 14.3 or higher

bundling packages/configs into modules

Would actually rather prefer building the necessary and dependency-related SBo .tgz's directly from the 14.2 SlackBuild repo itself https://slackbuilds.org/repository/14.2/development/ , and doing this within Slackware 14.2 itself rather than using Porteus via a repo mix-and-match fashion.
So for example, to install 'geany' along with the optional dependcies for 'geany-plugins' in SlackBuild.<pkg> order....

• geany: https://slackbuilds.org/repository/14.2 ... ent/geany/
• libwebp: https://slackbuilds.org/repository/14.2 ... s/libwebp/
• webkitgtk:https://slackbuilds.org/repository/14.2 ... webkitgtk/
• libunique: https://slackbuilds.org/repository/14.2 ... libunique/
• devhelp: https://slackbuilds.org/repository/14.2 ... t/devhelp/
• geany-plugins: https://slackbuilds.org/repository/14.2 ... y-plugins/

Once there are working <pkg>.tgz's in Slackware's /tmp directory, then can use USM (http://www.porteus.org/component/conten ... 9-usm.html) to convert geany*.tgz and geany-plugins*.tgz to Porteus's .xzm format for future module loading; see http://www.porteus.org/component/conten ... udies.html
Any possible problems with this?

On a bit of a negative note, seems that today's announcement 'Porteus-v5.0rc2 is released' at viewtopic.php?f=35&t=9179 shows a "lowlight" that USM is removed "with no replacement for now.."
If am sticking to using Porteus 4.0 though, then am totally okay with that

[ncmprhnsbl]

Once there are working <pkg>.tgz's in Slackware's /tmp directory, then can use USM

you can do this directly in a filemanager too(check the rightclick menu with a .tgz)
another approach is to bundle all the packages into one module .. eg:
1. put all the packages into a directory, eg: /tmp/pkgs
then

Code: Select all

# mkdir /tmp/geany
# ROOT=/tmp/geany installpkg /tmp/pkgs/*
# optional step: add configs and/or strip out things like headers, locales so on from this fakeroot
# dir2xzm /tmp/geany geany+deps.xzm (or whatever you want to call it)