Solved:LxQt /porteus/base (listed @ /var/log/packages)

[blue4meridian]

Salutations...

I'm interested in a copy (...of the "packages" preferably in separate folders for each "bundle"... eg. core.xzm)...

...of all the "packages" listed in each bundles /var/log/packages folder,
...for all the "bundles" in /porteus/base folder.

Best Regards...

[libernux]

Look in

Code: Select all

/mnt/live/memory/images

[blue4meridian]

Salutations...

Read the post carefully...

I know where the "base" is and where it's tree is (which can also be located by extracting the "base" modules).
I'm interested in the "PACKAGES"!!! that were used to make the "base" bundle tree so I can create a custom /porteus/base.

Best Regards...

[fanthom]

get packages from slackware + pkgs.org then convert them to modules.
please mind that with this method you'll get Slackware live rather than Porteus live (some Porteus specific cheatcodes and features will be missing).

or better:
- unpack core module
- run 'ROOT=/path/unpacked_module removepkg some_pkg' and the same for installpkg

reference:
http://www.fiveanddime.net/man-pages/installpkg.8.html

[blue4meridian]

Salutations...

I know where to get binary packages. I've noted the locations in numerous threads.
I'm interested in the "packages" that the devs used for LxQt Porteus
(I'm assuming thats how they made the "base" bundles).
A link (or ftp?) to those "packages" would save me countless hours of downloading from repos.

I assume one possible reason the devs used "base" bundles instead of modules is so n00bs won't brick the distro.
IMHO... I'm not a n00b and in any case I backup so bricking is moot.
If I break it I just fix it and reboot. That's why I switched from Android ( "rooting" hell?) to Porteus.

Whether USM or pkgs.org... (unlike a zip file containing ALL packages)
there is lots of entry... search... point... click... and download involved.

Based on the current LxQt loadout that's 454 downloads on a 25mbps netbook wifi (slower?) connection...

My goal is to tear the "base" to pieces and reconstruct it with drop-ins... eg. "useless daemon"...

Best Regards...

[fanthom]

I assume one possible reason the devs used "base" bundles instead of modules is so n00bs won't brick the distro.
IMHO... I'm not a n00b and in any case I backup so bricking is moot.
this is correct.

please contact me through fanthom@porteus.org and i will upload what i have for you. please mind that i wont provide ANY support for this and for the custom Porteus build you make. i simply have no time for this - sorry about that.

[neko]

@blue4meridian

I separate a module roughly into packages depending on the information of "/var/log/packages"
by the following script.
The unseparated results (symbolic linkages, etc.,) are separated manually.

#================================================================================
#! /bin/sh
move()
{
for DIR in `cat all/var/log/packages/$1 | sed -n '/^FILE LIST:$/,//p' | grep -v '^FILE LIST:$' | tr ' ' '!' `
do
if [ $DIR = "./" ]
then
continue
fi
DIR=`echo $DIR | tr '!' ' ' `
if [ -d "all/$DIR" ]
then
if [ ! -h "all/$DIR" ]
then
mkdir -p "pkg/$1/$DIR"
if [ "${DIR:0:10}" = "home/guest" ]
then
chown guest pkg/$1/$DIR
chgrp guest pkg/$1/$DIR
fi
continue
fi
fi
mv "all/$DIR" "pkg/$1/$DIR" 2>/dev/null
done
mkdir -p pkg/$1/var/log/packages
mv all/var/log/packages/$1 pkg/$1/var/log/packages/. 2>/dev/null
}

mkdir -p pkg
for PKG in `ls all/var/log/packages` ;
do
echo $PKG
move $PKG
done
#================================================================================

[blue4meridian]

Salutations...

Solved... I've given the issue careful thought. Maybe the best solution is uninstallment of the offending packages.
The posted command line approach sounds like a winner. The simplest approach is the one I'll sign up for.
If it's not posted then maybe it should be. @ fanthom... many thanks. You can remove the Kiosk "core" .tar server link.

Best Regards...

[Ed_P]

A very impressive script neko. Thank you for sharing it.