Differences

This shows you the differences between two versions of the page.

--- en:guides:makingtazpackages [2016/01/13 13:27]
brianperry
+++ en:guides:makingtazpackages [2016/01/28 15:07] (current)
brianperry
@@ Line 3: / Line 3: @@
 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).
-Then, it automatically puts all files you included in /fs/ into the correct place on the hard disk, overwriting old files bearing the same name, ... It knows where to place it 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 in /fs/usr/share/ in the package).
+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).
-After that, it executes the genpkg rules, ...
+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 !)
 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/ 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" or alternatively with a gui-based compression utility (like xarchiver, ...) \\
+    * 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 the following lines (replace "text" with your commands):
+    * 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>
-# Rules to gen a SliTaz package suitable for Tazpkg.
+compile_rules()
+{
+	text
+}
 genpkg_rules()
 {
@@ Line 18: / Line 22: @@
 }
-pre_remove()
+post_remove()
 {
 	text
@@ Line 38: / Line 42: @@
 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.
+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

en/guides/makingtazpackages.1452688024.txt.gz · Last modified: 2016/01/13 13:27 by brianperry

SliTaz Doc

Differences