| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| docs:guide-user:installation:sysupgrade.owut [2024/08/17 17:49] – [Command Line Options] Add links to descriptions efahlgren | docs:guide-user:installation:sysupgrade.owut [2024/08/18 20:34] – [List formatting] efahlgren |
|---|
| * ''fs-all'' - produces a package list for FS containing all top-level packages, which you'd paste //over// the values in the FS 'Installed Packages' field. | * ''fs-all'' - produces a package list for FS containing all top-level packages, which you'd paste //over// the values in the FS 'Installed Packages' field. |
| * ''config'' - produces a build ''.config'' snippet of user-installed, top-level packages that you can use when doing source builds. Each output line looks like ''CONFIG_PACKAGE_collectd-mod-thermal=y''. | * ''config'' - produces a build ''.config'' snippet of user-installed, top-level packages that you can use when doing source builds. Each output line looks like ''CONFIG_PACKAGE_collectd-mod-thermal=y''. |
| | |
| | The ''fs-*'' options generate lists in the Image Builder syntax, where mentioning a package name adds it to the list, and prefixing a package name with a dash removes it. |
| | |
| | For example, if you have installed ''dnsmasq-full'', then the default ''dnsmasq'' basic package must be removed. That would look like this (trimmed down for clarity): |
| | |
| | <code bash> |
| | $ owut list |
| | ... dnsmasq-full ... -dnsmasq ... |
| | </code> |
| | |
| | There are several packages provided by the defaults that are named using a generic package name, and actually provided by something with a different name, ''nftables'' is a prominent one (it is provided by either ''nftables-json'' or ''nftables-nojson'', there is no ''nftables'' package). ''owut'' appears to be removing it, but it really is just saying, "use the default, whatever that is". In the following example, we see only the ''-nftables'' removal, but not default package ''nftables-json'' as it will be added implicitly. |
| | |
| | <code bash> |
| | $ opkg whatprovides nftables |
| | What provides nftables |
| | nftables-json |
| | |
| | $ owut list |
| | ... -nftables ... |
| | </code> |
| | |
| | This can happen for other files that appear to be "deleted from nowhere" due to dependencies. As an example of this, if you are using ''luci-ssl-openssl'', then the list output will contain ''-libustream-mbedtls'' which would otherwise be added by defaults resulting in an "impossible package selection" error. |
| | |
| | You'll often see other evidence of these mappings when using ''check'' in the default package analysis results: |
| | <code> |
| | $ owut check |
| | ... |
| | Default package analysis: |
| | Default Provided-by |
| | dnsmasq dnsmasq-full |
| | kmod-dwmac-intel not installed |
| | nftables nftables-json |
| | ... |
| | </code> |
| |
| ==== Pre-install Script ==== | ==== Pre-install Script ==== |