QNAP NAS:Entware: различия между версиями

== Using repo ==

Entware uses OPKG package manager, detailed help can be found here. Lets find transmission packages and install it's Web UI with dependencies, just for example:

  Downloading http://bin.entware.net/mipselsf-k3.4/Packages.gz.

  Updated list of available packages in /opt/var/opkg-lists/entware.

</syntaxhighlight>

  transmission-cli - 2.84-4 - CLI utilities for transmission.

  transmission-daemon - 2.84-4 - Transmission is a simple BitTorrent client.

  transmission-web - 2.84-4 - Webinterface resources for transmission.

</syntaxhighlight>

  Installing transmission-web (2.84-4) to root...

  Downloading http://bin.entware.net/mipselsf-k3.4/transmission-web_2.84-4_mipselsf.ipk.

== Note about packages upgrade ==

In some rare cases you can fall into issue when new package wont start:

  minidlna: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory

</syntaxhighlight>

Unfortunately, **''%%opkg%%''** is too simple to track down **''%%minidlna%%''** dependencies has been changed and **''%%minidlna%%''** should be re-installed too. So, you have to do that manually:

Internals

</syntaxhighlight>

Entware uses OpenWrt buildroot to compile packages. Some of packages came from OpenWrt, others are unique. We sync our sources with OpenWrt feeds and update our own packages approx. once per month, catching bugs and adding some enhancements all other time.

See how to Compile packages from sources if you wish to edit or add packages.

Every binary from the repo uses no library from outside the /opt folder. No kernel modules are provided as long as they may be (and will be!) incompatible with current firmware.