Slax loads its modules on startup. If we put a lot of modules into modules dir the loading will be slower.
Thinking about this I'm evaluating to prepare bigger modules with some apps into them.
Ex: Firefox-Thunderbird-Pidgin with all dependencies.
I'd like to know if this choise will be appreciate.
Please comment with your suggestion on which apps I can put in groups.
Thank you.
Subscribe to:
Post Comments (Atom)

5 comments:
Thanks for your work on SLAX modules.
For me the most useful packages is "all-in-one" (with all dependences).
It would be quite good to build a package with libraries and programs for viewing djvu/chm/pdf files.
Ok, the packages "all-in-one" are useful, but if you use more packages may happen that you have the same libraries and dep. more times than only 1 that is enough.
My purpose was to prepare some modules and put in each one the most used apps with their libraries and dependencies (ex Mozilla Firefox, flash player, jre, Pidgin, and so on in only 1 module).
In these days here in Italy we have a little holiday, so I'm in mountainside and use HSDPA connection, so when I'll ack home I'll take a look at djvu, chm and pdf.
Well... djvu/chm/pdf it is just for an example... we use several books at these formats.
For viewing djvu files i'm using djvulibre, for chm - kchmviewer.
(all built with slackbuild scripts and tgz2lzm) I like your idea, so I plan to combine them into one package (djvulibre + xdg-utils + kchmviewer)
The kpdf, built in KDE works perfectly so others are not necessary.
I've taken a look at them and these are the packages I was going to use.
I haven't tested the dependencies, I'll do that on Tuesday when I'll back home.
Bye
I've seen that your choise is ok, you won't need any dep.
Bye
Post a Comment