Wiki has only manual how to create tar.gz packages.How does other packages are installed to the system?I just need to know how they differ from each oters and cons & pros.

I think I could contribute some packages. I can _easily_ create *.tbz2 packages on my primary system. (All compiled on Pentium III processor with newest compilers)

Also a small word about easy package "installation":If you have precompiled program inside tar package (compressed with gz/bz2 or not) you could use AVFS to mount almost any compressed file archive. Anyone considered usage of this in DSL? I haven't used AVFS. But it seems to have potetial to be very useful system utility.

.dsl means a .tar.gz, which writes to other places than just /opt, /home, and /tmp. It's just renamed to .dsl.

.uci is a clooped .iso, the concept is similar to .tar.gz - only write to /opt, be self-contained.

.unc is also a clooped iso, but it can write anywhere (using unionfs).

So, there are two main types of packages, and one unionfs/cloop variant of each.The main difference between unionfs and normal is smaller ram usage in livecd and frugal environments. They cannot be "permanently" installed, they have to be loaded on boot to archieve that effect. .dsl and .tar.gz can be installed permanently to HD installs, and .tar.gz can be installed permanently to frugal if you have persistent opt set up.

--------------There's no such thing as life. Those mean little jocks invented it ;)-Windows is not a virus. A virus does something!

It seems that easiest for me is to create .unc packages because I can create packages staright from my system with one command that collects all the files in the installation and adds them to tbz2 file. But .uci packages aren't hard either if it is a simple package (contains only few files).