PorteuX module builder

[rych]

Does PorteuX include any of the getpkg, pmod, getmod from Porteus ( Package Managers, Module Builders )

Or where do I get modules from? For example, I'd like to have ARandR to set up my monitors. It's included in Porteus, but I can also make it through

Code: Select all

root@porteus:~# getmod -s arandr
arandr-0.1.10-x86_64-2salix15.0  (ARandR: Another XRandR GUI)

Now, I'm on the "current" channel of PorteuX. Which Slackware version is it then, Slackware Current? Not Slackware 15 as my Porteus? So, I'd better have a package manager/module builder sourcing from right Slackware repositories, right? I can't just build a module on Porteus 5.0 for PorteuX Current?

[porteux]

Yes, getpkg and pmod are available out of the box. However, getmod isn't.

PorteuX current is in sync with Slackware current, while Porteux stable is in sync with Slackware 15.0.

In theory you can make a module for Porteus 5.0 and it should work in PorteuX current. Don't hurt trying

[Ed_P]

In theory you can make a module for Porteus 5.0 and it should work in PorteuX current.

The Porteus 5.0 003-cimmanon.xzm doesn't work in PorteuX.

Added in 18 minutes 24 seconds:
It looks like Porteus 5.0's getmod module might require PorteuX code tweaking.

Code: Select all

root@porteux:/home/guest# getmod

grep: warning: stray \ before -
grep: warning: stray \ before -

   getmod: A simple wrapper for slapt-get to build Porteus module.

   getmod [-c] [-u] [-d|-m|-M|-n|-N PACKAGE_NAME] [-l PATTERN] [-s PATTERN]

Options:

Added in 6 hours 11 minutes 34 seconds:
BTW Some getmod tweaks I found useful can be found in this posting: [Porteus 5.0's USM replacement] getmod: A wrapper for slapt-get to build modules (Post by Ed_P #92595)

[rych]

porteux, Although I installed PorteuX from porteux-v0.5-lxde-0.10.1-current-x86_64.iso, the word "current" doesn't seem to appear in my system leading to:

Code: Select all

root@porteux:~# slackpkg update
You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
but Slackware version 15.0+ appears to be installed.

Indeed:

Code: Select all

root@porteux:~# cat /etc/slackware-version
Slackware 15.0+

Proceeding nonetheless with a lengthy slackpkg update, I still get a surprising

Code: Select all

root@porteux:~# pmod -s arandr
Looking for arandr in package list. Please wait... DONE
No package name matches the pattern.

This finds nothing either and just exits:

Code: Select all

root@porteux:~# getpkg arandr
Searching in extra...
Searching in slackware64...

What else should I do? Or should this exercise decide for me which to use Slackware Current vs. Slackware 15: perhaps, Current is so incomplete that it doesn't even have basic utils such as Arandr?

[beny]

https://slackbuilds.org/repository/15.0/desktop/arandr/
Slackware 15.0+ the + is for current, if you want software for... you have to adress at sbo-git that is for the slackware current slackbuilds or you have to search here:
https://slackware.nl/slakfinder/index.p ... e=#results

[porteux]

@rych, arandr is not part of the official Slackware repository. As beny said, you'll need to build it using slackbuild -- and this should be pretty straightforward.

Regarding 'Slackware 15.0+', this is how Slackware refers to its current version, so this is not a PorteuX thing.

[rych]

I don't know how to

build it using slackbuild

In Porteus I rely on getmod/pmod to make modules and resolve dependencies for me.

When testing PorteuX, should I rather use PorteuX Stable which is on the same Slackware 15 as Porteus? That way, will I be able to share modules between Porteus and PorteuX (apart from base modules as described here https://github.com/porteux/porteux#comp ... -porteus-5)

[porteux]

@rych, it's a matter of trying. But I believe there's a mistake in the readme as PorteuX current should be more compatible because Porteus 5 has been released with a glibc version higher than Slackware 15.0, and this lib is very critical.

[rych]

PorteuX current should be more compatible because Porteus 5 has been released with a glibc version higher than Slackware 15.0, and this lib is very critical.

So, should I rather use PorteuX Current for more success when simply copying modules over from Porteus 5.0, or should I stay with PorteuX Stable?! By the way, I tried PorteuX Stable and pmod still didn't find the arandr. I know you said it is not part of the official Slackware repository. However, pmod on Poreteus 5.0 does find it. Maybe it's because of extra settings, like slackpkgplus.conf which I copied to PorteuX to no effect.

But actually, it's getmod that I want ideally and if it's not available in PorteuX, then I'm going to build my modules on Porteus and copy over to PorteuX. So, my question stands: in your opinion, should I rather use PorteuX Current or PorteuX Stable for this strategy?

[Ed_P]

should I rather use PorteuX Current or PorteuX Stable for this strategy?

PorteuX current should be more compatible

[rych]

PorteuX current should be more compatible

OK, I'm going back to Current.

Question: the only difference between Current and Stable are in the base modules explicitly stating stable/current variant in their name, so in my case I need to replace ONLY these back to *-current?

Code: Select all

/mnt/sda2/porteux/base/001-core-stable-20230710.xzm
/mnt/sda2/porteux/base/002-xorg-stable-20230710.xzm
/mnt/sda2/porteux/base/002-xtra-stable-20230710.xzm
/mnt/sda2/porteux/base/003-lxde-0.10.1-stable-20230710.xzm

[porteux]

@rych, yes, only these.

[Rava]

Regarding 'Slackware 15.0+', this is how Slackware refers to its current version, so this is not a PorteuX thing.

I presume that is when 15.0 is the most recent stable version?

E.g. when 'Slackware 13.37' was the most recent, then 'Slackware 13.37+' would have been current back then.
Same when we will have some day 'Slackware 16.0' - then the current would be 'Slackware 16.0+'

Do I presume correct?

[porteux]

Yes.