SliTaz GNU/Linux official and community documentation wiki.
.png
Translations of this page:

This is an old revision of the document!


Before starting on making slitaz packages, we'll begin with a quick overview of how a package installs programs:

When you click on a package to install (in tazweb), you tell the system to automatically download the package to /var/lib/tazpkg/5.0/packages/. It then automatically un-cpio's itself to ~/fs/ (or /home/tux/fs/ when using the absolute path).

Next, the packages are compressed: a folder called “fs” is cpio'ed and lzma compressed, and that .cpio.lzma folder is itself cpio'ed together with the receipt, files.list, md5sum, and description.txt into a cpio file renamed as filename.tazpkg

So, with this, we're all ready now to make a tazpackage:

# Rules to gen a SliTaz package suitable for Tazpkg. genpkg_rules() {

text

}

pre_remove() {

text

}

find . -type f -print > ../files.list 
find . -type l -print >> ../files.list
cd ..; sed -i s/'^.'/''/ files.list 

Alternatively, you can also do it using the tazpkg pack command; to see what that does exactly, see http://hg.slitaz.org/tazpkg/file/3af642cd5e69/modules/pack . In general it will make the md5 checksum and the filelist, and update the filesizes declared in the receipt. If you have already made the description and receipt it will also make the finished tazpackage in /home/tux (make sure you also pre-made the fs folder with the files therein for it to make a working tazpackage). Note that the wok too can be of use here (see http://doc.slitaz.org/en:oldcookbook:wok).

Once you have made a package, you can put it on a personal ftp site/webspace, or you can upload it to the slitaz package database using mercurial. See http://doc.slitaz.org/en:oldcookbook:wok on how to do this.

 
en/guides/makingtazpackages.1452543264.txt.gz · Last modified: 2016/01/11 21:14 by linea