Porteus

EDIT:
The bundles module is now available here
Please consider making bundles for your favourite desktop. Just boot into fresh mode with no extra modules and use USM to created a merged module, then upload it somewhere. Thanks.

Many users have been very active in creating modules lately. This is excellent and provides easily accessible modules to all users.

In an effort to make these even more accessible, what I propose is a system of creating a module with all dependencies included for a given architecture and desktop environment. Once tested the modules would be added to a server where a script from within porteus could search, download and activate the modules.

Pros: Guaranteed functionality, online activation, easy access
Cons: Doubled dependencies, larger module sizes

In my humble opinion the benefits outweigh the risks.

For this to work the following standards would need to be followed.

1) User boots into their desktop in 'Always fresh mode' (essential) to track dependencies

2) The target package and all of it's dependencies are installed into one folder and a module is made from this folder.

3) A single module is created that contains the architecture and desktop. This would be something like: mypackage-1.2.3-3.1-i486-xfce.xzm

4) A thread is posted in the modules section that contains the word 'bundle' in the heading.

Once the module is tested it is uploaded to our server and automatically becomes available from the Porteus side application. Anybody interested in beginning can start with modules already posted in the modules section. The focus should be on packages not already available in USM.

brokenman wrote:creating a module with all dependencies included for a given architecture and desktop environment

Request for Clarification

1. All dependencies for program to work out-of-the -box?
2. All dependencies for every conceivable use of program?
3. All dependencies for all packages dragged in by program?

1. All dependencies for program to work out-of-the -box

Don't we have to get a porteus version number in somewhere?

Very good idea brokenman. This will provide a better use of the productivity and creativity of the members of the community. In addition, the time needed for installation will be so short, porteus will be more attractive and taken as a more serious distribution.

Which it is already, don't read me wrong.

Thanks Bogomips, updated with version number. This is important.

I hope it is popular Francois. The community has been producing many modules lately so we might as well make them easily accessible.

a) i would add 'porteus' word to bundle name to not confuse the version b) maybe single libs could be accepted in the bundle instead of full packages to avoid size? eg if tigervnc requires 'fltk-1.3.so' then add just this lib and not whole fltk package. this way we would have full application + required libs in the bundle. this idea is optional and for advanced users only.

What about modules that run fine on multiple versions of Porteus?
??

And who will update the module names as they are found to run on newer Porteus versions?

maybe porteus3.x for all 3 line (slackware 14.1) and porteus3.1 when only for 3.1 (due to upgraded libs in the desktop module or something...)

Procedural Questions

1. Okular is in 003-kde.xzm, and is supposed to do both pdf and ps. There is a dependency requirement for postscript file handling. Designate dependency module as okular-ps-dep-0.0.0porteus3.0.1-i486-kde.xzm or just okular-dep-0.0.0porteus3.0.1-i486-kde.xzm ?
2. 06-abiword.xzm does not work out-of-the-box, so should there just be a dependency bundle abiword-dep-0.0.0porteus3.0.1-i486.xzm or a complete bundled abiword-0.0.0porteus3.0.1-i486.xzm ?

you need libspectre to get ps to work in KDE4.
not sure about abiword but all modules we maintain should work with every DE. something for brokenman to check ...

Post deleted.

@fanthom

Been using the bundles in order to use Okular, and in oder to use Abiword. They have already been tested on a barebones kde. All I have to do is to put them up. Just wish to know how to designate them for Brokenman's project. Does he require Abiword bundled together with dependencies? Also wish to know which module designation he would prefer.

What I had in mind for bundles was not 'addon' files but complete applications.

06-abiword.xzm does not work out-of-the-box

Can you explain this a little further please?

a complete bundled abiword-0.0.0porteus3.0.1-i486.xzm

This would be preferred. Please upload this bundle for abiword and I will see if I can add it to the official release.

The naming convention should be: abiword-0.0.0-porteus3.1-i486-kde.xzm or abiword-0.0.0-porteus3.1-i486-alldesktops.xzm

Is there any additional development coming out for this project?