SliTaz Repositories

     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/pages/en/guides/faq-pkgconv.txt	Sat Feb 26 12:17:18 2011 +0000
     1.3 @@ -0,0 +1,21 @@
     1.4 +====== Packages from Other Distributions ======
     1.5 +
     1.6 +===== Symptoms =====
     1.7 +
     1.8 +  * There is a useful package that is not yet available in the SliTaz repositories.
     1.9 +  * Can I use packages from other distributions on my SliTaz installation?
    1.10 +
    1.11 +===== Explanation =====
    1.12 +
    1.13 +Packages in a general sense are simply a collection of files and meta-data, compiled from source code to suit a particular environment and installation. Software binaries from other distributions can sometimes run if the libraries that power it exist for SliTaz. It is an easy but not-always-accurate way of testing packages before writing SliTaz [[en:cookbook:receipt | Receipts]] for a SliTaz version of the package.
    1.14 +
    1.15 +The SliTaz Package Manager, Tazpkg, can [[http://hg.slitaz.org/tazpkg/raw-file/tip/doc/tazpkg.en.html#convert | convert]] packages from the Debian, RedHat, Slackware and Arch Linux formats, by unpacking them and using the meta-data information inside to create a Tazpkg.
    1.16 +
    1.17 +===== Solution =====
    1.18 +
    1.19 +Simply run the following command in a Terminal:
    1.20 +''tazpkg convert //filename//''
    1.21 +
    1.22 +The converted Tazpkg will be created after auto-detection of the original format.
    1.23 +
    1.24 +<note important>There may be occasions where the generated package does not function. This could be a result of mismatching libraries or missing dependant software. Similarly, the binaries may under-perform as they may have been compiled for a different environment and have to adapt. For these reasons, it is highly advisable to compile the software from source code and create a Tazpkg proper.</note>
    1.25 \ No newline at end of file