Porteus

discussion was started here:
http://forum.porteus.org/viewtopic.php?f=53&t=229
please read it first.

this is the list of packages which i would like to include in 003-Libraries-Utils.
following packages could be moved from existing modules to it:

./001
./001/python-2.6.6-x86_64-1.xzm
./001/tcl-8.5.9-x86_64-1.xzm
./001/tclx-8.4-x86_64-3.xzm
./001/tk-8.5.9-x86_64-1.xzm
./002
./002/cups-1.4.6-x86_64-1.xzm
./002/giflib-4.1.6-x86_64-1.xzm
./002/librsvg-2.32.0-x86_64-1.xzm
./002/pycairo-1.8.10-x86_64-1.xzm
./002/pygobject-2.26.0-x86_64-1.xzm
./002/pygtk-2.22.0-x86_64-1.xzm
./002/rdesktop-1.6.0-x86_64-1.xzm
./002/sdl-1.2.14-x86_64-3.xzm
./002/wicd-1.7.0-x86_64-2.xzm
./003
./003/gpicview-0.2.1-x86_64-1ponce.xzm
./003/xarchiver-0.5.2-x86_64-3ponce.xzm
./004
./004/exiv2-0.21-x86_64-1ftm.xzm
./004/libmng-1.0.10-x86_64-2.xzm
./005
./005/cdrtools-3.01a02-x86_64-1.xzm
./005/djvulibre-3.5.22-x86_64-2.xzm
./005/dvd+rw-tools-7.1-x86_64-1.xzm
./005/flac-1.2.1-x86_64-2.xzm
./005/cdrdao-1.2.3-x86_64-1ftm.xzm
./005/faad2-2.7-x86_64-1ftm.xzm
./005/lame-3.98.4-x86_64-1ftm.xzm
./005/libcddb-1.3.2-x86_64-1ftm.xzm
./005/libcdio-0.82-x86_64-1ftm.xzm
./005/libva-0.32.0_p2-x86_64-1ftm.xzm
./005/libvdpau-0.4.1-x86_64-1ftm.xzm
./005/vdpau-video-0.7.3-x86_64-1ftm.xzm
./005/libdvdread-4.1.3-x86_64-1.xzm
./005/libmad-0.15.1b-x86_64-3.xzm
./005/libogg-1.2.0-x86_64-1.xzm
./005/libsamplerate-0.1.7-x86_64-2.xzm
./005/libsndfile-1.0.23-x86_64-1.xzm
./005/libvorbis-1.3.2-x86_64-1.xzm
./005/MPlayer-20110127-x86_86-1ftm.xzm
./005/xvba-video-0.7.8-x86_86-1ftm.xzm
./005/taglib-1.6.3-x86_64-1.xzm
./005/wavpack-4.60.1-x86_64-1.xzm

/porteus/base should look like:

000-kernel
001-core
002-xorg
003-libraries-utilities
004-lxde
005-kde
006-devel
007-firefox-flash

any other changes, propositions? what else could be moved and where?

So far I approve, if I think of proposition(s) I will tell you...

Maybe I think of propositions once porteus 1.0 beta runs (depends if I made no error with neoGrub, and for now it runs from NTFS sharing that with Windoze7... )

If it works fine , i am agree !

So 005/006 would be merged with 004?

hnmmm... now i'm thinking it makes no sense....
maybe instead of creating a new module i could:
- move 'cdrtools' to 001-core (so new ISO could be created no matter of used modules)
- move 'mplayer' + all required libs to 002-xorg (it would be available for all desktops: kde, lxde, gnome, etc.. i hope we have not so many 'vlc' fans here:) )
- merge 004-kde + 005-kdeapps together (KDE is short of apps anyway. i dont believe that anybody is removing 005-kdeapps as he would get broken taskbar and almost nothing on his desktop)

which option is better:
1) create new xzm module - 003-libraries-utilities
2) rebase existing modules + merge 005-kdeapps with 004-kde so we would have 6 modules only:

000-kernel
001-core
002-xorg
003-lxde
004-kde
005-devel
006-firefox-flash

i would be opting on second choice...

fanthom wrote:- move 'cdrtools' to 001-core (so new ISO could be created no matter of used modules)

I fully agree here, it could be the core of an non X system with some basic functionality like creating isofs and burning CDROMs and DVDs...

- move 'mplayer' + all required libs to 002-xorg (it would be available for all desktops: kde, lxde, gnome, etc.. i hope we have not so many 'vlc' fans here:) )

Now, mplayer runs in virtual console as well, but only makes sense with music, not with video...
So I agree as well...

- merge 004-kde + 005-kdeapps together (KDE is short of apps anyway. i dont believe that anybody is removing 005-kdeapps as he would get broken taskbar and almost nothing on his desktop)

Again: I fully agree.

Yes i like second option. koffice can be offered as a module. I removed ALOT of stuff from koffice and would be nice to have it all as a module. There are quite a few packages spread across 004/005/006 with icons & .desktop files in 004 and bins/libs in 005. Will be nice to merge them.

There is also alot of gnome fans ... so maybe something to look at in the future as an optional module.

unless it was changed in beta (32-bit), I think wpa_supplicant and its's dependency, dbus, should go in 001-base. thoughts?

dbus needs some X libs and i'm not sure if it's able to work without them properly. will check it soon.
in case of troubles i would leave wpa_supplicant and dbus in 002-xorg.

Ahh, I see. I probably had some X related files installed when I pulled wpa and dbus over.

by the way, what package do you have installed instead of gcc-java? I'm not a fan of needing a 20+MB dep around just for getting 007-devel to work (with 002-xorg removed).

thanks!

just moved wpa_supplicant and dbus to 001 and seems to be ok.
i will stay with it so even CLI freaks can be connected to the hotspots and use lynx for browsing

"what package do you have installed instead of gcc-java?"
nothing - this dependency is unresolved (same for mysql).

Cheers

@fanthom
I forgot to ask one thing...

When creating the XFCe only Slax 6.1.2. I realized that the "popup" speech bubble that tells the user that a module is being loaded and later is being successfully loaded did not work without the KDE modules.
I tried to extract the needed files but I did not succeed.

Any idea what these might be?
And in my book these dependencies should be moved in a module like "002-xorg" so that more than KDE can use this feature...

@Rava
all scripts were rewritten against Xdialog and moved to 002-xord so 'double-click' activation/deactivation of the modules will work for all desktop possible.
it's done in BETA's already.

Ahhh fine then....
I know I should be running the 1.0 beta more, to be able to give more input and maybe help more with debug; but still the V08 is my "productive stable" release... *shrug*

If I would find a way to fix my broken keyboard for my Samsung Q40 on the other hand....