- Put all packages going to make up the module in a new work directory
- If all packages have extension *.txz or *.tgz, go to 5.
- Convert RPM packages using rpm2txz
- Using (latest version in thread of) Script to make Slackware Compliant package of xz, deb
- Convert .deb:
Code: Select all
sh deb2txz.sh -nv [/path to package/]<package>.deb
- Convert .xz:
Code: Select all
sh xz2txz.sh -nv [/path to package/]<package>.xz
- Convert .deb:
- Create a Fakeroot DirectoryAs Root:
Code: Select all
mkdir fkr
Create ModuleCode: Select all
# installpkg --terse --root fkr *.t?z
Code: Select all
# dir2xzm fkr <name of desired module>.xzm
Making Modules without RTFM
-
- Full of knowledge
- Posts: 2564
- Joined: 25 Jun 2014, 15:21
- Distribution: 3.2.2 Cinnamon & KDE5
- Location: London
Making Modules without RTFM
Making a Module from a Collection of Packages
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
- Ed_P
- Contributor
- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: Making Modules without RTFM
I thought francois said we weren't suppose to use abbreviations cause some members don't know what they mean. So you need to change the title.
Its interesting to note that while Porteus has so many GUI tools built in most posts to fix problems are terminal examples. Don't get me wrong, they are effective and solve the problems, and I for one have learned a lot from them. And these steps I could have used a few days ago when I was trying to combine some modules.

Its interesting to note that while Porteus has so many GUI tools built in most posts to fix problems are terminal examples. Don't get me wrong, they are effective and solve the problems, and I for one have learned a lot from them. And these steps I could have used a few days ago when I was trying to combine some modules.
-
- Full of knowledge
- Posts: 2564
- Joined: 25 Jun 2014, 15:21
- Distribution: 3.2.2 Cinnamon & KDE5
- Location: London
Re: Making Modules without RTFM
^ Suppose it is that one really does not have the time to play around with the GUIs, unless a GUI really takes the strain from the brain, which the ISO FIle Editor does.
As for abbreviations, those universally known in the Linux world are to the best of my knowledge allowed. Francois himself has seen fit to provide RTFM together with its long form: 'Read the Fine Manual". 8)

Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
- wread
- Module Guard
- Posts: 1257
- Joined: 09 Jan 2011, 18:48
- Distribution: Porteus v5.0-kde-64 bits
- Location: Santo Domingo
- Contact:
Re: Making Modules without RTFM
My version of RTFM is not so fine; neither that of "foobar"!
(fine on our bastard aknowledgment requirement)

Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!
The Porteus Community never sleeps!
- francois
- Contributor
- Posts: 6499
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: Making Modules without RTFM
There is also, simply, but positively:
Read The Fine Manual
Read The Fine Manual
Prendre son temps, profiter de celui qui passe.