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 [2010/07/12 21:06] seawolf explanation of get-* packages |
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 47: | Line 47: | ||
| * remove it by using tazpkg on the **generated** package. | * remove it by using tazpkg on the **generated** package. | ||
| - | \\ | + | <note tip>Please note that after downloading the //get-package//, you need to run the script that has the same name: |
| + | <code> # tazpkg get-install get-OpenOffice3 | ||
| + | # get-OpenOffice3</code> | ||
| + | </note> | ||
| === Upgrade installed packages === | === Upgrade installed packages === | ||
| Line 53: | Line 56: | ||
| To keep your system up-to-date and secure after recharging the packages list, you can automatically install all new versions and security updates from the mirror with the command: | To keep your system up-to-date and secure after recharging the packages list, you can automatically install all new versions and security updates from the mirror with the command: | ||
| - | <code> # tazpkg upgrade </code> | + | <code> # tazpkg up </code> |
| === Tazpkg Manual === | === Tazpkg Manual === | ||
| Line 59: | Line 62: | ||
| The Tazpkg [[http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html|Manual]] contains a lot more useful information. | The Tazpkg [[http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html|Manual]] contains a lot more useful information. | ||
| - | ===== Tazwok & the wok ===== | + | ===== Cookutils & the wok ===== |
| - | All SliTaz packages are built with a tool named Tazwok 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, Tazwok 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. |
| - | Tazwok 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 Tazwok configuration file which can be located in ///etc/tazwok.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> # tazwok new-tree pkgname --interactive </code> | + | <code> # cook new pkgname --interactive </code> |
| When a new package tree and receipt has been created in the wok, you can edit the receipt with your favorite editor (Geany provides nicely colored code), modify the rules, functions, add dependencies to the DEPENDS variable if needed and try a first cook: | When a new package tree and receipt has been created in the wok, you can edit the receipt with your favorite editor (Geany provides nicely colored code), modify the rules, functions, add dependencies to the DEPENDS variable if needed and try a first cook: | ||
| - | <code> # tazwok cook pkgname </code> | + | <code> # cook pkgname </code> |
| - | Note that you can now browse the generated files, modify the cooking receipt again or just rebuild the package with tazwok genpkg. When you are happy with your work you can install the package with tazpkg install and then test the application or library. | + | Note that you can now browse the generated files, modify the cooking receipt again or just rebuild the package. When you are happy with your work you can install the package with tazpkg install and then test the application or library. |