Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:guides:makingtazpackages [2016/01/09 12:03] brianperry |
en:guides:makingtazpackages [2016/01/28 15:07] (current) brianperry |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Before starting on making slitaz packages, we'll begin with a quick overview of how a package installs programs: | 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). | + | 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, how the packages are compressed: | + | Then, it automatically puts all of the files you included in /fs/ into the correct place on the hard disk, overwriting the old files bearing the same name, ... It knows where to place them as you use the exact same path of the files as the path the files are installed to on your harddisk (so if for instance, you want the package to copy a file called foo.bar to /usr/share, put foo.bar into /fs/usr/share/ in the package). |
| - | a folder called "fs" is cpio'ed and lzma compressed, and that .cpio.lzma folder is itself cpio'ed together with receipt, files.list, md5sum, and description.txt into a cpio file renamed as filename.tazpkg | + | |
| - | So, with this, we all ready now how to make a tazpackage: | + | After that, it executes the compile rules, genpkg rules, ... (assuming you packed it with tazwok; if packed with tazpkg it won't call these rules !) |
| - | * put all the files/folders you need in /fs/ and compress this as cpio, and then as lzma (do this using the cpio-command "cpio -o -H newc --quiet ", and the lzma-command "xz --format=lzma fs.cpio.lzma fs.cpio" | + | |
| - | * put the file size details of the copi.lzma folder in the receipt (you can find these by right-clicking-->properties in PCManFm on the file). Also put in the following lines (replace "text" with your commands): | + | So, with this, we're all ready now to make a tazpackage ourselves: \\ |
| + | * put all the files/folders you need in /fs/path_of_files/ ; make sure the fs contents only contains binaries, scripts, configuration files, ... It should not contain source files, license, readme's, ... Compress the files as cpio, and then as lzma (do this using the cpio-command "cpio -o -H newc --quiet ", and the lzma-command "xz --format=lzma fs.cpio.lzma fs.cpio" or alternatively with a gui-based compression utility (like xarchiver, ...) \\ | ||
| + | * put the file size details of the cpio.lzma folder in the receipt (you can find these by right-clicking-->properties in PCManFm on the file). Also put in the following lines (replace "text" with your commands; for more rules, see http://doc.slitaz.org/en:cookbook:receipt): | ||
| <note tip> | <note tip> | ||
| - | # Rules to gen a SliTaz package suitable for Tazpkg. | + | compile_rules() |
| + | { | ||
| + | text | ||
| + | } | ||
| genpkg_rules() | genpkg_rules() | ||
| { | { | ||
| Line 17: | Line 22: | ||
| } | } | ||
| - | pre_remove() | + | post_remove() |
| { | { | ||
| text | text | ||
| Line 23: | Line 28: | ||
| </note> | </note> | ||
| - | * make the files.list file by cd-ing to your tazpkg's fs folder, and then using following commands: | + | * make the files.list file by cd-ing to your tazpkg's fs folder, and then using following commands: \\ |
| - | find . -type f -print > ../files.list | + | <code> |
| + | find . -type f -print > ../files.list | ||
| find . -type l -print >> ../files.list | find . -type l -print >> ../files.list | ||
| - | cd ..; sed -i s/'^.'/''/ files.list | + | cd ..; sed -i s/'^.'/''/ files.list |
| + | </code> | ||
| + | |||
| + | * make the md5 file by typing the command "md5sum filename", or by using a program (on windows, you can use winmd5, FCIV, certutil, hashtab, hashcheck, ...) | ||
| + | |||
| + | * compress the fs.cpio;lzma file together with the receipt, files.list, md5sum, and description.txt into a cpio file renamed as filename.tazpkg . Do so by using the cpio compress command: cpio -oH < fs.cpio.lzma receipt files.list md5sum description.txt > filename.tazpkg or using a gui-based compression utility (like xarchiver, ...) | ||
| - | * make the md5 file by typing the command "md5sum filename". | + | Alternatively, you can also make the package by 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). |
| - | * compress the whole by using the cpio compress command: cpio -oH < fs.cpio.lzma receipt files.list md5sum description.txt > filename.tazpkg | + | 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. |
| - | 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 | + | Also note you may also want to read: \\ |
| + | http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html \\ | ||
| + | http://hg.slitaz.org/cookutils/raw-file/tip/doc/cookutils.en.html | ||