Thanks for providing the custom build feature on the firmware selector. Have tried it recently and found it very useful. When I had tried it many months ago, it didn't seem to work for my device. Works good now.
When doing a custom build on the selector is it supposed to include all dependencies? I saw a previous question, but there wasn't a definitive answer.
I included luci-app-wireguard and the resulting image did not have luci which should be a dependent package imho.
Couple comments the workflow is a bit confusing. After it completes, the list of packages reverts to the default list. That left me wondering if it built what I asked or not. Of course checking size, hashses and downloading I was able to confirm that it did.
I was looking for a more general answer on dependencies not just what happens with luci.
Based on some more testing, I would say it like this.
The custom image builder handles dependencies. Generally, luci-app-X packages do not include luci as a dependency, therefore luci must be explicitly added to the package list.
Example case. luci-app-travelmate.
Note: Looks likek you need to use the -A in the opkg command to get the dependencies to output.
It has these dependencies:
root@tplinktest:/tmp# opkg depends -A luci-app-travelmate
luci-app-travelmate depends on:
And travelmate has these:
root@tplinktest:/tmp# opkg depends -A travelmate
travelmate depends on:
I've checked first few luci apps when listed alphabetically and most (tho not all yet) luci apps dependencies include either luci-compat or luci-base or luci-mod-admin-full, my understanding is that either of these should bring luci with it.
@jow can you please clarify in which cases the new (js-based) luci apps should depends on luci-base or luci-mod-admin-full and if luci-compat depends on either of these? Between me, @dibdot and @hnyman I'm sure we can do a tree-wide edit to include the proper luci components int he Makefiles.
@stangri I did spot check a few. I should have said I was looking for experts to confirm. This topic goes deeper than I knew.
root@tplinkrouter:/tmp# opkg depends -A luci-app-firewall
luci-app-firewall depends on:
root@tplinkrouter:/tmp# opkg depends -A luci-app-nextdns
luci-app-nextdns depends on:
root@tplinkrouter:/tmp# opkg depends -A luci-app-sqm
luci-app-sqm depends on:
@lleachii With the questions around luci, it wasn't clear to me what the builder did regarding dependencies in general. I think I understand now. For my travelmate test, I included luci-app-travelmate and the dependency caused it to include travelmate and the nested dependency caused it to include curl. That is how I got to, 'The custom image builder handles dependencies.'