Slax author's Blog (RSS)
10
January2013
Best practices for building Slax modules II
I've extended the documentation for best practices by the followint paragraphs. Feel free to share your opinion about them. Thanks!

User comments


1/ Don't make too many errors like Tomas M :-D
--- "Removeing" [...]
--- "followint" [...]
2/ Do a correct numbering in releases :
I do recommend something like :
softwareName-1.2.3.4-20130101.build.i486.
softwareName-docs-1.2.3.4-20130101.build.i486.
3/ Docs should be as expected:
a) the software run as explained
b) the options are ALL well documented [if pictures are needed it must be in the docs directory]
c) the document is acurate AND up to date [such as www.sqlite.org]
d) examples must be provided : It is a good idea to provide a file that could be used to make all the tests...
e) Licence must be clear [I've seen licence that I do not understand]


Guys I just wanted to point out that the build script should make sure that all *.pc files get copied to /usr/share/pkgconfig because some ./configure scripts check module presence via pkg-config --modversion and some make install scripts don't put it in the right dir, they just leave it in source dir, so maybe that should be in best practices too :)

And also there seems to be some bug with slax module activating/deactivating
when you have module already activated and in folder modules, and call slax activate same_module, sometimes it says module already activated and sometimes it says cannot deactivate same_module or cannot remove /modules/same_module.sb .. and when I remove it by hand rm .. module... and call slax activate again, it magically works ...
and /modules/* has 777 permissions ...
what is this?

Oh yess, it tries to download the bundle again and the file is already there, so it stops and doesnt activate it... that seems to me like a bug, it should detect the file, check if it is the same size or MD5 and in that case activate the file itself and not try downloading nothing, and if size/md5 check fails, remove the file and download it again, but in either case, it should activate the module no matter what, except for some serious trouble :)


And that is the reason why my build fails on the server, because it tries to activate the modules, and I think it deactivates them after the build so it could build other modules without all of the previous ones activated right? so when it tries to activate them again it fails. ... and when I activate them manualy from the file location and not by command, the build succedes on my machine
@Tomas: you sould look into this, not because of my modules, but because this is kind of core of slax :)

I've started a thread on the old forum where I write down some things I come across while using slax all day, and trying to compile stuff and create buildscripts
http://old.slax.org/forum.php?action=view&parentID=83850

I fond kernel source module in server and downloaded it . But it's a old version .
Hmmm ext4 and they are all 777. Interesting. Only time that happens for me is when the drive is Fat32 or NTFS.

@mark read the description in the forum thread and try that for yourself if you have the time



Fine! A bad example is already there (djvulibre, k3b, etc).
I want to make the modules. There is nobody more.
Credit of trust is out (from 10 to 17 seat for 2 days at Distrowatch.com).
Too long absent: Office suite, printer support, burn discs. Curvature-abyss. Sorry for the same curve English. Hard to keep quiet.
Want a minimalist, learn here: ftp://austrumi.ru.lv/austrumi-2.6.0.iso
Want to have worked, learn here: http://www.porteus.org http://www.magos-linux.ru

Austrumi + translations + Woof ... potential.
I haven't been able to access porteus pages for days.
MagOS = Mandriva-scripts + linux-live?

@ Somewhat Reticent 2013-01-13 21:45
Porteus gone dark?
http://old.slax.org/forum.php?action=view&parentID=82945&highlight=porteus%20gone%20dark
They are there as always . They are as busy as ever , with kde4 , qtrazor and even gnome desktop version...

I gave links to other distros, not because they are better.
They are worse, more bugs, but there are the most needed applications.
Slax users can ask Tomas, instead of learning how to make modules, set an example and do you need: printing support, burn discs, Office applications, java, etc.
Need a special section for error messages to see a true picture of the curvature.

About best practices documentation:
I miss some info about architecture dependency. Shall all modules be for example i486 compatible or may there be optimized modules. If so, they should be tagged as such.
In Slax6 there has been a configure-for-slax wrapper script that set some recommended variables.

Folks! Folks! Can you hear me? Or am I the only one greedy?
And you do not need anything?
Here are the contents of my folders /modules :
120-btrfs-progs.sb,126-cups.sb,188-rpm2tgz.sb,309-gcc-java.sb,1068-xkill.sb,1196-kernel-firmware.sb,partitionmanager.sb - this is Tomas M. modules.
The author knows that better than most users need. As always. "Best practices!!!"
cndrvcupscapt.sb, cndrvcupscommon.sb, conky.sb, deadbeef.sb, GParted.sb, iconsIceglass4.0.sb, java-jre.sb, k3b.sb, Luckybackup.sb, Opera.sb, Photo.sb, Pinta.sb, SimpleBurn.sb, SoftmakerFreeOffice.sb, umplayer.sb, Skype.sb, XnviewMP.sb, Wine.sb, wuala.sb - These are my modules. Without any rules. "Best practices!!!"
Left to do: Libre/OpenOffice; + Understand what's missing print and burn disk. "Best practices!!!"

"what's missing print and burn disk. "
You already add k3b.sb -burn disk
For printing
http://old.slax.org/forum.php?action=view&parentID=83472&highlight=printpack
http://old.slax.org/forum.php?action=view&parentID=83628&highlight=printpack

Thank you. I got it. I'm lost.
Crap boils - http://old.slax.org/
Pops up pearls- http://slax.org/

@ Tomas
http://old.slax.org/forum.php?action=view&parentID=83850
Post no 16 by Stopa
"Just as was the slax 6
I have two computers with NVidia and Radeon
Depending on where they work I would like to choose between loading the driver module Nvidia or Radeon."
I think he have a valid ground for requiring the "no load" cheatcode or would you suggest how to choose between nvidia/radeon module in slax
7 .
He can't be the only user facing this problem ?


Perhaps include references to documentation? After all, documentation is a discipline that results in better code. But it shouldn't be code. Except for truth-in-labeling, of course. Which can be pop-up on hover ...