wiki:keros_custo:package_management
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wiki:keros_custo:package_management [2019/09/25 17:02] ghi |
wiki:keros_custo:package_management [2022/10/24 16:49] (current) ehe [Accepted Architectures] |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| * ''cortexa9hf-neon-mx6sx'' architecture is not longer valid and must be replaced by ''armv7ahf-neon'' | * ''cortexa9hf-neon-mx6sx'' architecture is not longer valid and must be replaced by ''armv7ahf-neon'' | ||
| - | Starting from version 4.1, KerOS firmwares are usable on all Wirnet™ Productline gateways. Product arch is ''klkgw'' for all gateways. | + | Starting from version 4.1, KerOS firmwares are usable on all Wirnet™ i-series gateways. Product arch is ''klkgw'' for all gateways. |
| ==== Accepted Architectures ==== | ==== Accepted Architectures ==== | ||
| Line 25: | Line 25: | ||
| To sum up the accepted package's architectures on the gateways, you can consult the following table: | To sum up the accepted package's architectures on the gateways, you can consult the following table: | ||
| - | ^ Firmware Version ^ Gateway ^^^ | + | ^ Firmware Version ^ Gateway ^^^^ |
| - | ^ ::: ^ Wirnet™ iFemtoCell ^ Wirnet™ iBTS ^ Wirnet™ iStation ^ | + | ^ ::: ^ Wirnet™ iFemtoCell ^ Wirnet™ iBTS ^ Wirnet™ iStation ^ Wirnet™ iFemtocell-Evolution ^ Wirnet™ iZeptoCell | |
| - | ^ KerOS v4.0 | armv7ahf-neon\\ klk_wifc | armv7ahf-neon\\ klk_lbps | @red:Not supported | | + | ^ KerOS v4.0 | armv7ahf-neon\\ klk_wifc | armv7ahf-neon\\ klk_lbps | @red:Not supported | @red:Not supported | @red:Not supported | |
| - | ^ KerOS v4.1 | armv7ahf-neon\\ klk_wifc\\ klkgw | armv7ahf-neon\\ klk_lbps\\ klkgw | armv7ahf-neon\\ klkgw | | + | ^ KerOS v4.1 | armv7ahf-neon\\ klk_wifc\\ klkgw | armv7ahf-neon\\ klk_lbps\\ klkgw | armv7ahf-neon\\ klkgw | @red:Not supported | @red:Not supported | |
| + | ^ KerOS v4.2 | ::: | ::: | ::: | armv7ahf-neon\\ klkgw | @red:Not supported | | ||
| + | ^ KerOS v5.x | ::: | ::: | ::: | ::: | armv7ahf-neon\\ klkgw | | ||
| <note important>Please note that the **klkgw** architecture is accepted on every product since KerOS v4.1! So package maintainer MUST integrates a detection of the product (if necessary) in order to adapt its behavior</note> | <note important>Please note that the **klkgw** architecture is accepted on every product since KerOS v4.1! So package maintainer MUST integrates a detection of the product (if necessary) in order to adapt its behavior</note> | ||
| Line 77: | Line 79: | ||
| - | If this operation is not done, the system could become unstable if the package is removed because the original file will not be automatically restored. Instead the file will simply be removed. | + | If this operation is not done, the system could become unstable if the package is removed because the original file will not be automatically restored. Instead, the file will simply be removed. |
| ===== Building your own package ===== | ===== Building your own package ===== | ||
| Line 128: | Line 130: | ||
| </code> | </code> | ||
| - | To generate a package, the tools ''opkg-build'' requires a directory tree containing all the files to copy, all scripts and the meta-data file. The following script generates the directory tree as well as the files populating it. Then it creates the packet itself. To do so, 6 steps are required: | + | To generate a package, the tools ''opkg-build'' require a directory tree containing all the files to copy, all scripts and the meta-data file. The following script generates the directory tree as well as the files populating it. Then it creates the packet itself. To do so, 6 steps are required: |
| - Downloading ''opkg-build'' if not already done. | - Downloading ''opkg-build'' if not already done. | ||
| - Generating a ''control'' file containing meta-data in the ''CONTROL'' folder. | - Generating a ''control'' file containing meta-data in the ''CONTROL'' folder. | ||
| Line 173: | Line 175: | ||
| Priority: optional | Priority: optional | ||
| Section: test | Section: test | ||
| - | Source: Kerlink's Wirnet(TM) Productline wiki | + | Source: Kerlink's Wirnet(TM) i-series wiki |
| Description: Install two files in userland | Description: Install two files in userland | ||
| EOF | EOF | ||
| Line 269: | Line 271: | ||
| To get the list of backuped packages use the following command: | To get the list of backuped packages use the following command: | ||
| <code bash> | <code bash> | ||
| - | root@klk-lpbs-0507DD:/.update/packages/backup # ll /.update/packages/backup/ | + | root@klk-lpbs-0507DD: ll /.update/packages/backup/ |
| drwxr-xr-x 2 root root 4.0K Jun 5 15:29 . | drwxr-xr-x 2 root root 4.0K Jun 5 15:29 . | ||
| drwxr-xr-x 4 root root 4.0K Jun 5 15:00 .. | drwxr-xr-x 4 root root 4.0K Jun 5 15:00 .. | ||
| Line 316: | Line 318: | ||
| </code></note> | </code></note> | ||
| - | The package can be generated using ''opkg-build'' binary. Procedure hereunder is dedicated to Linux operating systems. There is no embedded compiler in Wirnet™ Productline gateways. | + | The package can be generated using ''opkg-build'' binary. Procedure hereunder is dedicated to Linux operating systems. There is no embedded compiler in Wirnet™ i-series gateways. |
| <code bash> | <code bash> | ||
wiki/keros_custo/package_management.1569423722.txt.gz · Last modified: 2019/09/25 17:02 by ghi
