Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:handbook:packages [2012/04/06 21:03] linea |
en:handbook:packages [2016/03/31 19:36] genesis [Tazpkg - Package manager] |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| === Install packages === | === Install packages === | ||
| - | To install some new applications such as The Gimp, AbiWord, ePDFView, Perl or Python, you first need to recharge the list of available packages on the mirror and then install. If the package dependencies are not installed, Tazpkg will install them for you. For example, the installation of Gparted a GTK+ partition editor using GNU parted: | + | To install some new applications such as The Gimp, AbiWord, ePDFView, Perl or Python, you first need to recharge the list of available packages on the mirror and then install. If the package dependencies are not installed, Tazpkg will install them for you. For example, the installation of Gparted (a GTK+ partition editor using GNU parted): |
| <code> | <code> | ||
| Line 66: | Line 66: | ||
| All SliTaz packages are built with a tool named Cookutils and a receipt found in the wok. The receipt provides all the necessary information to build a suitable package for Tazpkg including variables to give us the package name, source tarball format, download URL, etc. Given a receipt, the compile_rules function has all of the necessary commands to configure, make, and install the package in a specific directory. After compilation, Cookutils will execute the function genpkg_rules to pick up only the needed/wanted files and generate a pkg.tazpkg (cpio archive). On SliTaz you will find all installed package receipts in the directory ///var/lib/tazpkg///installed, feel free to examine them or even use one as an example. | All SliTaz packages are built with a tool named Cookutils and a receipt found in the wok. The receipt provides all the necessary information to build a suitable package for Tazpkg including variables to give us the package name, source tarball format, download URL, etc. Given a receipt, the compile_rules function has all of the necessary commands to configure, make, and install the package in a specific directory. After compilation, Cookutils will execute the function genpkg_rules to pick up only the needed/wanted files and generate a pkg.tazpkg (cpio archive). On SliTaz you will find all installed package receipts in the directory ///var/lib/tazpkg///installed, feel free to examine them or even use one as an example. | ||
| - | Cookutils will search by default for a wok in ///home/slitaz/wok// and put generated packages in ///home/slitaz/packages//. These paths are set by a Cookutils configuration file which can be located in ///etc/slitaz/cook.conf// or in the current directory, which is useful if you want to work with multiple woks. Now, if the slitaz-toolchain is installed, you can start to create and build a package which doesn't need many dependencies. Small example: | + | Cookutils will search by default for a wok in ///home/slitaz/wok// and put generated packages in ///home/slitaz/packages//. These paths are set by a Cookutils configuration file which can be located in ///etc/slitaz/cook.conf// or in the current directory, which is useful if you want to work with multiple woks. Now, if the Cookutils are setup (//# cook setup//) and the slitaz-toolchain is installed, you can start to create and build a package which doesn't need many dependencies. Small example: |
| <code> # cook new pkgname --interactive </code> | <code> # cook new pkgname --interactive </code> | ||