port wrote: ↑06 Aug 2017, 09:24
know what minimum files must be included in such a module, I suppose the minimum must be all files needed by the wm/desktop but maybe others are also needed, like slim.conf etc
pretty much, and slim itself of course..
(one way)to find out what else is included (that isnt part of a package) would be:
as root
1. extract(dir2xzm or rightclick>extract module) the module somwhere (POSIX compatible fs or /tmp if you have plenty of ram)
2. do
Code: Select all
ROOT=/path/to/extracted/module removepkg <list of all the packages in the module>
3.whats left should be anything added that isnt part of a package
or get the build scripts and look at the relevant 'TREE' file :
Re: What license and where are the sources? (Post by brokenman #49401)
similarly, if you want remove anything you dont want, use the
removepkg command for that .. and
installpkg for something you want to include..
(there is also commands: extractpkg and upgradepkg) (bear in mind: some things you dont want may be in 002-xorg)
(other useful commands: ldd /usr/bin/<foo> (to check for missing libs) and usm -d (to check for missing deps)
port wrote: ↑06 Aug 2017, 09:24
I think it would be better not including it in core xfce module and split it into xfce-tools module or something like that
this is a fair enough idea, and has been explored to some degree in the Nemesis(arch based) side project(in hiatis) with its base modules thus:
00-kernel 001-core 002-gui 002-xtra 003-shared 003-lxde 003-lxde-xtra (or something like that)
from what i am aware of present porteus development, this type of structure isnt a priority, and development direction has a certain enertia..
that said, thing with porteus is that it come with the tools necessary to customise it to however you like..
for example, you boot without 003-<DE> (cheatcode: login=root noload=003 ) , you get a openbox session with xterm, mc, nmtui(for wifi) and usm to get what you want..
Added in 9 minutes 59 seconds:
port wrote: ↑06 Aug 2017, 09:24
simlink the one I want to use in $PORTDIR/modules
what i use is the
load=<module/string> boot line cheatcode that parses the optional folder (and the
noload=<module/string> that inhibits modules in base or modules..