slpkg for porteus 5.0: getting it to work.

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

slpkg for porteus 5.0: getting it to work.

Post#1 by francois » 02 Oct 2022, 13:27

slpkg is a package manager (binaries) and builder (from source or sbo).

Final release of porteus 5.0 provided us with package managers and tools, namely slackpkg, slpkg, pmod and pkginfo.
Porteus-v5.0 is released!

Rereading the above thread, though I had read it already a few times, I just felt like a child facing a christmas tree full of gifts.

I have tried to work with slpkg which really interested me a few years ago.
slpkg : package builder (manager) linux

slpkg very convincing video. You have to look at it.
https://www.youtube.com/watch?v=oTtD4XhHKlA

Lets use the pkginfo tool to see if slpkg on the system:

Code: Select all

root@porteus:/home/guest# pkginfo -w slpkg

 Package:  slpkg-3.9.6-x86_64-1_ncm  
 located in Module:  05-devel.xzm 

root@porteus:/home/guest# slpkg -h
Traceback (most recent call last):
  File "/usr/bin/slpkg", line 35, in <module>
    from slpkg.main import main
ModuleNotFoundError: No module named 'slpkg'
root@porteus:/home/guest# 
It seems I am stuck here.

I am working with porteus 5 xfce desktop.

Any solution would be appreciated.

Thanks.
Prendre son temps, profiter de celui qui passe.

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

slpkg for porteus 5.0: getting it to work.

Post#2 by Rava » 02 Oct 2022, 14:23

Even worse for me:

Code: Select all

guest@porteus:~$ pkginfo -w slpkg

 slpkg is not in any modules.
Having the need to activate the massive 05-devel for only getting slpkg to try it out is overkill for me.

Creating a module using pmod fails:

Code: Select all

root@porteus:~# pmod -s slpkg

Looking for slpkg in package list. Please wait... DONE

No package name matches the pattern.
:shock:

Okay, trying slapt-get / getmod next.
(Be right back…)

Added in 2 minutes 7 seconds:
Good that I now have my activate script for 011-slapt-get so that the symlink creation is done automatically.

Code: Select all

root@porteus:~# activate-011-slapt-get 
activate-011-slapt-get V0.1
activate /mnt/sda5/Porteus_modules/5.0/011-slapt-get-0.11.6-x86_64-2gv.xzm
Updating shared library links:  /sbin/ldconfig
cd /var/lib/pkgtools/packages
'gtk+3-3.24.33-x86_64-1' -> 'gtk3-classic-3.24.33-x86_64-2ncm'
'boost-1.78.0-x86_64-1' -> 'boost-stripped-1.78.0-x86_64-2_slack15.0'
'llvm-13.0.0-x86_64-1' -> 'llvm-stripped-13.0.0-x86_64-2'
(Be right back…)

Added in 6 minutes 11 seconds:

Code: Select all

root@porteus:~# getmod -m slpkg
Reading Package Lists...Done
The following NEW packages will be installed:
  slpkg 
0 upgraded, 0 reinstalled, 1 newly installed, 0 to remove, 0 not upgraded.
Need to get 138.0kB of archives.
Do you want to continue? [y/N] y
1/1 Get http://slackware.uk/salix/x86_64/extra-15.0/ slpkg 3.9.8-x86_64-1salix15.0 [138.0kB]...Done

Done
Verifying package slpkg-3.9.8-x86_64-1salix15.0.txz.
Installing package slpkg-3.9.8-x86_64-1salix15.0.txz:
PACKAGE DESCRIPTION:
# slpkg (Slackware Packaging Tool)
#
# Slpkg is a powerful software package manager that installs, updates
# and removes packages on Slackware based systems. It automatically
# computes dependencies and figures out what things should occur
# to install packages. Slpkg makes it easier to maintain groups of
# of machines without having to manually update.
#
# Homepage: https://dslackw.gitlab.io/slpkg
#
Executing install script for slpkg-3.9.8-x86_64-1salix15.0.txz.
Package slpkg-3.9.8-x86_64-1salix15.0.txz installed.
Parallel mksquashfs: Using 8 processors
Creating 4.0 filesystem on /tmp/slpkg-3.9.8-x86_64-1salix15.0.xzm, block size 1048576.
[=================================================================-] 90/90 100%

Exportable Squashfs 4.0 filesystem, zstd compressed, data block size 1048576
	compressed data, compressed metadata, compressed fragments,
	compressed xattrs, compressed ids
	duplicates are removed
Filesystem size 52.05 Kbytes (0.05 Mbytes)
	14.02% of uncompressed filesystem size (371.19 Kbytes)
Inode table size 1084 bytes (1.06 Kbytes)
	26.37% of uncompressed inode table size (4110 bytes)
Directory table size 1309 bytes (1.28 Kbytes)
	49.28% of uncompressed directory table size (2656 bytes)
Number of duplicate files found 1
Number of inodes 127
Number of files 90
Number of fragments 1
Number of symbolic links 3
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 34
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)

====> '/tmp/slpkg-3.9.8-x86_64-1salix15.0.xzm' was created successfully.
Yay!

Code: Select all

root@porteus:~# slpkg -h
Traceback (most recent call last):
  File "/usr/bin/slpkg", line 35, in <module>
    from slpkg.main import main
  File "/usr/lib64/python3.9/site-packages/slpkg/main.py", line 58, in <module>
    from slpkg.sbo.queue import QueuePkgs
  File "/usr/lib64/python3.9/site-packages/slpkg/sbo/queue.py", line 39, in <module>
    from slpkg.sbo.slack_find import slack_package
  File "/usr/lib64/python3.9/site-packages/slpkg/sbo/slack_find.py", line 26, in <module>
    from pkg_resources import parse_version
ModuleNotFoundError: No module named 'pkg_resources'
Nay!
And not quite the same errors as you got, francois.

My system XFCE 4.12 on Port 5.0 x86-64.

And it never worked that well for me in trying to solve python dependency issues in the past. :wall:

Added in 1 minute 54 seconds:
Looks like in 05-devel some dependency issues got solved for slpkg - but not all.

Added in 1 minute 44 seconds:
And getmod did not report any additional needed packages either when I did the getmod -m slpkg

Added in 1 minute 5 seconds:
francois wrote:
02 Oct 2022, 13:27
It seems I am stuck here.
So am I… Image
Cheers!
Yours Rava

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

slpkg for porteus 5.0: getting it to work.

Post#3 by babam » 02 Oct 2022, 15:02

Rava,

Reinstall python3

Code: Select all

# removepkg python3
# getmod -m python3
Sorry, my English is bad.

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

slpkg for porteus 5.0: getting it to work.

Post#4 by beny » 02 Oct 2022, 15:25

Code: Select all

guest@porteus:~$ sudo slpkg

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: 
Usage: slpkg [COMMANDS|OPTIONS] {repository|package...}

             Commands:
             [update, --repositories=[...]]
             [upgrade, --repositories=[...]]
             [repo-add [repository name] [URL]]
             [repo-remove [repository]]
             [repo-enable]
             [repo-list]
             [repo-info [repository]]
             [update [slpkg]]
             [health, --silent]
             [deps-status, --tree, --graph=[type]]
             [new-config]
             [clean-tmp]

             Optional arguments:
             [-h] [-v]
             [-a [script] [sources...]]
             [-b [package...] --add, --remove,
                 [list]]
             [-q [package...] --add, --remove,
                 [list, build, install, build-install]]
             [-g [print, edit, reset]]
             [-l [repository], --index, --installed, --name]
             [-c [repository], --upgrade, --rebuild, --skip=[...],
                               --resolve-off, --checklist]
             [-s [repository] [package...], --rebuild, --reinstall,
                                            --resolve-off, --download-only,
                                            --directory-prefix=[dir],
                                            --case-ins, --patches]
             [-t [repository] [package], --check-deps, --graph=[type],
                                         --case-ins]
             [-p [repository] [package], --color=[]]
             [-n [SBo package], --checklist, --case-ins]
             [-F [package...], --case-ins]
             [-f [package...], --case-ins, --third-party]
             [-i [options] [package...]]
             [-u [options] [package...]]
             [-r [options] [package...], --deps, --check-deps, --tag,
                                         --checklist, --third-party]
             [-d [package...]]
             
For more information try 'slpkg -h, --help' or view manpage

guest@porteus:~$ 
hello slpkg is included in the devel module, but considering, now with getmod to pmod we have everything we need
but managing gslapt packages and even slakfinder outside pmod or getmod are useless, salix and extra salix repositories are very complete so better to use a tool that makes things easier,and if I read correctly slpkg now only deals with slackbuild packages but I can be wrong

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

slpkg for porteus 5.0: getting it to work.

Post#5 by Rava » 02 Oct 2022, 16:00

babam wrote:
02 Oct 2022, 15:02
Rava,

Reinstall python3

Code: Select all

# removepkg python3
# getmod -m python3
You mean to say, some stuff was stripped from python and that's the reason why slpkg is not working?

If so… how does one make a diff between the system's setup and when I did

Code: Select all

# removepkg python3
# getmod -m python3
I know diff can also be done on 2 paths and then diff lists every file or folder that differs between the paths to examine, but would that help in figuring out what needs to be added to get slpkg running?
Having removepkg python3 and getmod -m python3 everytime one wants to use slpkg is impractical, to say it nicely.
_________________________________________

beny, how did you get slpkg to run?
Did you do removepkg python3 and getmod -m python3 or do you use a different DE that has some more python dependencies?
Cheers!
Yours Rava

beny
Full of knowledge
Full of knowledge
Posts: 2086
Joined: 02 Jan 2011, 11:33
Location: italy

slpkg for porteus 5.0: getting it to work.

Post#6 by beny » 02 Oct 2022, 16:03

the usual one porteus5 xfce4.16 i have a python 3.10 but is on optional directory so is sleeping ,well i don't do this for run slpkg
and have a deps SQLAlchemy

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

slpkg for porteus 5.0: getting it to work.

Post#7 by Rava » 02 Oct 2022, 23:31

beny wrote:
02 Oct 2022, 16:03
the usual one porteus5 xfce4.16 i have a python 3.10 but is on optional directory so is sleeping ,well i don't do this for run slpkg
and have a deps SQLAlchemy
So you did not activate the python 3.10 module for slpkg
but you did activate the SQLAlchemy dependency module?

Can you post what's in your /mnt/live/memory/images when you ran slpkg please?
do

Code: Select all

cd /mnt/live/memory/images
ls
and put the result into a [ code ] area - that's the [</>] icon on top of your edit area. Thanks.
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

slpkg for porteus 5.0: getting it to work.

Post#8 by ncmprhnsbl » 03 Oct 2022, 00:31

what the... see here: Porteus-v5.0 is released! (Post by ncmprhnsbl #88441)
says:
and slpkg (in 05-devel)
slpkg helps with building from sbo.. it requires some python elements that are in 05-devel(plus whatever other compiling tools needed) (maybe it does 'normal' packages too, i forget)
you do not need to reinstall python and you certainly do not need python 3.10 (which isn't even in slackware current)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

slpkg for porteus 5.0: getting it to work.

Post#9 by Rava » 03 Oct 2022, 03:25

^
Indeed… Don't know what's different with francois Port 5.0 XFCE (aside he using the 4.16 version and me the 4.12 version of XFCE) but kicking out 011-slpkg-3.9.8-x86_64-1salix15.0.xzm and activating 05-devel.xzm instead makes slpkg work out of the box:

Code: Select all

root@porteus:/mnt/live/memory/images# activate /mybin/linux/porteus/5.0/x86-64/05-devel.xzm 
Updating shared library links:  /sbin/ldconfig
Updating MIME database:  /usr/bin/update-mime-database /usr/share/mime
Updating GDK pixbuf loaders: /usr/bin/update-gdk-pixbuf-loaders
Updating GDK pixbuf loaders: /usr/bin/update-gdk-pixbuf-loaders

root@porteus:/mnt/live/memory/images# slpkg --version
Version   : 3.9.6
Licence   : GNU General Public License v3 (GPLv3)
Email     : d.zlatanidis@gmail.com
Homepage  : https://dslackw.gitlab.io/slpkg/
Maintainer: Dimitris Zlatanidis (dslackw)
Added in 1 minute 40 seconds:
05-devel.xzm is of course this version

Code: Select all

root@porteus:/# md5sum /mybin/linux/porteus/5.0/x86-64/05-devel.xzm 
4ad2c0217ec914cb02aab3b77fd55fe5  /mybin/linux/porteus/5.0/x86-64/05-devel.xzm

root@porteus:/# ls -o --time-style=long-iso /mybin/linux/porteus/5.0/x86-64/05-devel.xzm| cut -c 21-
48471808 2022-07-03 11:00 /mybin/linux/porteus/5.0/x86-64/05-devel.xzm
Added in 6 minutes 3 seconds:
My system:

Code: Select all

root@porteus:~# cat /etc/porteus/*
001-core.xzm:20220723
002-xorg.xzm:20220723
002-xtra.xzm:20220630
003-xfce4.xzm:20220428
initrd.xz:20201102
As usual, XFCE reports a wrong version. It is 003-xfce-4.12-20220725 and not 20220428
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

slpkg for porteus 5.0: getting it to work.

Post#10 by ncmprhnsbl » 03 Oct 2022, 07:09

yeah, most likely the newer version from salix would work too with 05-devel active
so anyway, i don't know what's going on with francois' setup, slpkg not finding it's own (python)module suggests something is messed up(either some other (porteus) module or in changes ... so check with a 'clean' system.

some tips for slpkg:
the help info:

Code: Select all

# slpkg -h
slpkg - version 3.9.6 | Slackware release: stable - 15.0

Slpkg is a user-friendly package manager for Slackware installations

Usage: slpkg [COMMANDS|OPTIONS] {repository|package...}

                                                   _       _
                                               ___| |_ __ | | ____ _
                                              / __| | '_ \| |/ / _` |
                                              \__ \ | |_) |   < (_| |
                                              |___/_| .__/|_|\_\__, |
                                                    |_|        |___/
                                             _Slackware package manager_______

Commands:
   update, --repositories=[...]              Run this command to update all
                                             the packages lists.

   upgrade, --repositories=[...]             Delete and recreate all packages
                                             lists.

   repo-add [repository name] [URL]          Add custom repository.

   repo-remove [repository]                  Remove custom repository.

   repo-enable                               Enable or disable default
                                             repositories via dialog utility.

   repo-list                                 Print a list of all the
                                             repositories.

   repo-info [repository]                    Get information about a
                                             repository.

   update slpkg                              Upgrade the program directly from
                                             repository.

   health, --silent                          Health check installed packages.

   deps-status, --tree, --graph=[type]       Print dependencies status used by
                                             packages or drawing dependencies
                                             diagram.

   new-config                                Manage .new configuration files.

   clean-tmp                                 Clean the tmp/ directory from
                                             downloaded packages and sources.
Optional arguments:
  -h | --help                                Print this help message and exit.

  -v | --version                             Print program version and exit.

  -a | --autobuild, [script] [source...]     Auto build SBo packages.
                                             If you have already downloaded the
                                             script and the source code you can
                                             build a new package with this
                                             command.

  -b | --blacklist, [package...] --add,      Manage packages in the blacklist.
       --remove, list                        Add or remove packages and print
                                             the list. Each package is added
                                             here will not be accessible by the
                                             program.

  -q | --queue, [package...] --add,          Manage SBo packages in the queue.
       --remove, list, build, install,       Add or remove and print the list
       build-install                         of packages. Build and then
                                             install the packages from the
                                             queue.

  -g | --config, print, edit, reset          Configuration file management.
                                             Print, edit the configuration file
                                             or reset in the default values.

  -l | --list, [repository], --index,        Print a list of all available
       --installed, --name                   packages from repository, index or
                                             print only packages installed on
                                             the system.

  -c | --check, [repository], --upgrade,     Check for updated packages from
       --rebuild --skip=[...],               the repositories and upgrade or
       --resolve-off, --checklist            install with all dependencies.

  -s | --sync, [repository] [package...],    Sync packages. Install packages
       --rebuild, --reinstall,               directly from remote repositories
       --resolve-off, --download-only,       with all dependencies.
       --directory-prefix=[dir],
       --case-ins, --patches

  -t | --tracking, [repository] [package],   Tracking package dependencies and
       --check-deps, --graph=[type],         print package dependencies tree
       --case-ins                            with highlight if packages is
                                             installed. Also check if
                                             dependencies used or drawing
                                             dependencies diagram.

  -p | --desc, [repository] [package],       Print description of a package
       --color=[]                            directly from the repository and
                                             change color text.

  -n | --network, [package], --checklist,    View a standard of SBo page in
       --case-ins                            terminal and manage multiple
                                             options like reading, downloading,
                                             building, installation, etc.

  -F | --FIND, [package...], --case-ins      Find packages from each enabled
                                             repository and view results.

  -f | --find, [package...], --case-ins,     Find and print installed packages
       --third-party                         reporting the size and the sum.

  -i | --installpkg, [options] [package...]  Installs single or multiple *.tgz
       options=[--warn, --md5sum, --root,    (or .tbz, .tlz, .txz) Slackware
       --infobox, --menu, --terse, --ask,    binary packages designed for use
       --priority, --tagfile]                with the Slackware Linux
                                             distribution onto your system.

  -u | --upgradepkg, [options] [package...]  Upgrade single or multiple
       options=[--dry-run, --install-new,    Slackware binary packages from
       --reinstall, --verbose]               an older version to a newer one.

  -r | --removepkg, [options] [package...],  Removes a previously installed
       --deps, --check-deps, --tag,          Slackware binary packages,
       --checklist, --third-party            while writing a progress report
       options=[-warn, -preserve, -copy,     to the standard output.
       -keep]                                Use only package name.

  -d | --display, [package...]               Display the contents of installed
                                             packages and file list.

You can read more about slpkg from manpage or see examples from readme file.
Issues: https://gitlab.com/dslackw/slpkg/issues
Homepage: https://dslackw.gitlab.io/slpkg/
the config files:

Code: Select all

# ls /etc/slpkg
blacklist             pkg_security       slackware-mirrors
custom-repositories   repositories.conf  slpkg.conf
default-repositories  rlworkman.deps     slpkg.conf.orig
read them, they're mostly self explanatory
ones to note: slpkg.conf ... probly ok as is .. maybe change EDITOR=nano to your favourite editor
repositories.conf ... only slackware and sbo enabled atm enable what you want
slackware-mirrors ... uncomment someplace nearby will probly work better for you
blacklist ... handy for deps you don't want/need or already have by a different name

looking at https://dslackw.gitlab.io/slpkg/
seems like much has changed since 3.9.6 >> 4.1.7
looks like the new version only handles sbo
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

slpkg for porteus 5.0: getting it to work.

Post#11 by Rava » 03 Oct 2022, 07:18

ncmprhnsbl wrote:
03 Oct 2022, 07:09
maybe change EDITOR=nano to your favourite editor
do change it, while nano is a nice console based editor in its own right, we do not have it by default:

Code: Select all

guest@porteus:/tmp$ nano
bash: nano: command not found
I suggest replacing it with mcedit - every Porteus system should have it (it's the standalone version of the internal editor of mc, in case someone did not know) and since it has a text-based GUI and menus and text-based "windows" (like settings) can be interacted with using the mouse, most users should feel at ease using mcedit from the get-go.
In comparison to, say, vim, which I also use but new users will be overwhelmed by how vim is operating. ":wq" or ":q!" is not intuitive, the w or q part is, but not the initial ":" part.
Last edited by Rava on 03 Oct 2022, 07:20, edited 1 time in total.
Reason: added bold and colours
Cheers!
Yours Rava

User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

slpkg for porteus 5.0: getting it to work.

Post#12 by francois » 03 Oct 2022, 16:30

@ncmprhnsbl:
Acknowledging that slpkg is for building from source. Thanks for pointing to /etc/slpkg/slpkg.conf where repositories seemed to be.

I had devel.xzm, but I confess that I did it with changes. :oops:

I will try with a clean new system. :roll:

Rereading my old thread on slpkg a video seems very convincing. You have to look at it. Following citation is from the author of the youtube video:
https://www.youtube.com/watch?v=oTtD4XhHKlA
Slpkg is a powerful software package manager that installs, updates, and removes packages on Slackware based systems. It automatically computes dependencies and figures out what things should occur to install packages. Slpkg makes it easier to maintain groups of machines without having to manually update.

The big question is will it accomodate a wide variety of repositories.
Prendre son temps, profiter de celui qui passe.

User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

slpkg for porteus 5.0: getting it to work.

Post#13 by francois » 04 Oct 2022, 20:20

Will it accomodate a wide variety of repositories?
The answer is that it accomodates a lot of repositories.
:)
Prendre son temps, profiter de celui qui passe.

User avatar
francois
Contributor
Contributor
Posts: 6434
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

slpkg for porteus 5.0: getting it to work.

Post#14 by francois » 05 Oct 2022, 23:49

Using always fresh I get the same problem:

Code: Select all

root@porteus:/home/guest# slpkg -h
Traceback (most recent call last):
  File "/usr/bin/slpkg", line 35, in <module>
    from slpkg.main import main
ModuleNotFoundError: No module named 'slpkg'
root@porteus:/home/guest# slpkg update
Traceback (most recent call last):
  File "/usr/bin/slpkg", line 35, in <module>
    from slpkg.main import main
ModuleNotFoundError: No module named 'slpkg'
root@porteus:/home/guest# 
I will get rid of every modules and then see.
Prendre son temps, profiter de celui qui passe.

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

slpkg for porteus 5.0: getting it to work.

Post#15 by Rava » 06 Oct 2022, 01:10

francois wrote:
05 Oct 2022, 23:49
I will get rid of every modules and then see.
Get rid of every module?
Really? Including the likes of 000-kernel.xzm and 001-core.xzm?
Please report how that worked out, you got me curious. :D
Cheers!
Yours Rava

Post Reply