a2bda4cc69
While the idea may make sense the current implementation is faulty. Problem is that OpenWrt uses the folder name of packages within the build system while `opkg` spits out the actual packages names. An example, compiling the packages of folder `vim` (`make package/vim/compile`) creates a package called `xxd`, where `make package/xxd/compile` would fail. The current implementation uses `opkg` to figure out dependent packages, but the resulting names do not match the above mentioned folders. Revert this for now until we come up with a better implementation to avoid false positive CI failures. Signed-off-by: Paul Spooren <mail@aparcar.org> |
||
---|---|---|
.circleci | ||
.github | ||
.keys | ||
admin | ||
devel | ||
fonts/dejavu-fonts-ttf | ||
ipv6 | ||
kernel | ||
lang | ||
libs | ||
multimedia | ||
net | ||
sound | ||
utils | ||
.travis.yml | ||
.travis_do.sh | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md |
README.md
OpenWrt packages feed
Description
This is the OpenWrt "packages"-feed containing community-maintained build scripts, options and patches for applications, modules and libraries used within OpenWrt.
Installation of pre-built packages is handled directly by the opkg utility within your running OpenWrt system or by using the OpenWrt SDK on a build system.
Usage
This repository is intended to be layered on-top of an OpenWrt buildroot. If you do not have an OpenWrt buildroot installed, see the documentation at: OpenWrt Buildroot – Installation on the OpenWrt support site.
This feed is enabled by default. To install all its package definitions, run:
./scripts/feeds update packages
./scripts/feeds install -a -p packages
License
See LICENSE file.
Package Guidelines
See CONTRIBUTING.md file.