I am please to announce the avaibility of BETA version of Astware/Entware for Asustor x86, x86_64 and armhf (not tested) models ...
Tested only on AS5002T and AS202TE under 2.5 beta firmware ...
Entware is a modern replacement for the abandoned Optware/ipkg (not maintained, updated (package and security))
[History]
Entware was developed to replace Optware/ipkg (abandoned) for router especially using Mipsel processor architecture
Zyxmon ( http://www.zyxmon.org/ ), thanks to him, have made a port on x86 and armel architecture (first for some NAS) then a port to Armhf (armv7) architecture never supported by Optware/ipkg
To avoid conflicts with existing Optware he design two different approach
... for x86, x86_64, armel ... (Qnapware) he use /Apps/opt in place of /opt for installing (this need a total PATH change in package)
... for armhf ... he keep Entware using /opt ... target is at end to move ALL to /opt to don't have risk of error due to PATH modification ...
Astware/Entware is on same model :
... for x86, x86_64 ... use /Apps/opt
... for armhf ... use /opt
Astware/Entware is a ALL IN ONE apk ... so during install the correct version (architecture) is installed depend of processor type ...
Entware is independent of Asustor libraries and loader (ex. Entware use loader and libs 2.20 when Asustor use 2.13) ... so it's a more complete separation between each even using a (small) more memory by duplicating libs ...
[Name]
Astware 0.90
[Prerequisite]
Best : have an internet access active and working during installation :
... at end of install and update of package list is done then a first package (need to be complete) is installed
BUT this can be done later using a console if you don't have access to internet during installation
[Potential Bugs]
NOT tested (no system) on armhf ... so I search beta testers ...
Conflict with Asustor implementation (order of apk start) ... Asustor use /opt in some case (structure and link for Chrome-Sandbox) ... this is NOT a problem up we use /opt for x86
[Packages]
1600+ ... list : http://entware.wl500g.info/binaries/ent ... kages.html Packages are updated one per month
changelog (version updated) : https://github.com/Entware/entware/wiki/Changelog
Specific packages from Zyxmon exist like Deluge 1.3.12 + addons, iotop, etc. exist also
Wiki : https://github.com/Entware/entware/wiki (adapt to Asustor implementation)
Issues and bugs report : https://github.com/Entware/entware/issues (only issue for Entware packages)
[Usage]
One command compatible with old ipkg one : opkg
An auto start services mechanism exist to start background process (all is provide to run your own)
Code: Select all
# opkg
opkg must have one sub-command argument
usage: opkg [options...] sub-command [arguments...]
where sub-command is one of:
Package Manipulation:
update Update list of available packages
upgrade Upgrade installed packages
install <pkgs> Install package(s)
configure <pkgs> Configure unpacked package(s)
remove <pkgs|regexp> Remove package(s)
flag <flag> <pkgs> Flag package(s)
<flag>=hold|noprune|user|ok|installed|unpacked (one per invocation)
Informational Commands:
list List available packages
list-installed List installed packages
list-upgradable List installed and upgradable packages
list-changed-conffiles List user modified configuration files
files <pkg> List files belonging to <pkg>
search <file|regexp> List package providing <file>
find <regexp> List packages whose name or description matches <regexp>
info [pkg|regexp] Display all info for <pkg>
status [pkg|regexp] Display all status for <pkg>
download <pkg> Download <pkg> to current directory
compare-versions <v1> <op> <v2>
compare versions using <= < > >= = << >>
print-architecture List installable package architectures
depends [-A] [pkgname|pat]+
whatdepends [-A] [pkgname|pat]+
whatdependsrec [-A] [pkgname|pat]+
whatrecommends[-A] [pkgname|pat]+
whatsuggests[-A] [pkgname|pat]+
whatprovides [-A] [pkgname|pat]+
whatconflicts [-A] [pkgname|pat]+
whatreplaces [-A] [pkgname|pat]+
Options:
-A Query all packages not just those installed
-V[<level>] Set verbosity level to <level>.
--verbosity[=<level>] Verbosity levels:
0 errors only
1 normal messages (default)
2 informative messages
3 debug
4 debug level 2
-f <conf_file> Use <conf_file> as the opkg configuration file
--conf <conf_file>
--cache <directory> Use a package cache
-d <dest_name> Use <dest_name> as the the root directory for
--dest <dest_name> package installation, removal, upgrading.
<dest_name> should be a defined dest name from
the configuration file, (but can also be a
directory name in a pinch).
-o <dir> Use <dir> as the root directory for
--offline-root <dir> offline installation of packages.
--add-arch <arch>:<prio> Register architecture with given priority
--add-dest <name>:<path> Register destination with given path
Force Options:
--force-depends Install/remove despite failed dependencies
--force-maintainer Overwrite preexisting config files
--force-reinstall Reinstall package(s)
--force-overwrite Overwrite files from other package(s)
--force-downgrade Allow opkg to downgrade packages
--force-space Disable free space checks
--force-postinstall Run postinstall scripts even in offline mode
--force-remove Remove package even if prerm script fails
--force-checksum Don't fail on checksum mismatches
--noaction No action -- test only
--download-only No action -- download only
--nodeps Do not follow dependencies
--nocase Perform case insensitive pattern matching
--force-removal-of-dependent-packages
Remove package and all dependencies
--autoremove Remove packages that were installed
automatically to satisfy dependencies
-t Specify tmp-dir.
--tmp-dir Specify tmp-dir.
regexp could be something like 'pkgname*' '*file*' or similar
e.g. opkg info 'libstd*' or opkg search '*libop*' or opkg remove 'libncur*'
APKG : https://mega.nz/#!U5U0xZja!K60RkRUAtabq ... SAiTw2hvkU
Size : 2816020 B
Md5 : 0ffae8a3300b498f72643c0f8d8120de
Install manually .
have fun.
Philippe.