Topic: About "missing" packages in Barrier Breaker and trunk
We decided to reorganize the packages feed in June, since lots of the
packages in there were unmaintained and we had lot's of patches we
couldn't review. The new feed resides on github which makes contributing
more straigt-forward. See https://github.com/openwrt/packages
The old feed is now referred to as "oldpackages".
Now the problem with packages like python or php in "oldpackages" is
that they build a version which have known security issues, so providing
binaries for them without notice is a bit dubious. Note: we didn't
delete any package-definitions we just stopped building binaries. Once
someone takes over maintainership for them and keeps them updated we
will gladly welcome them in our new packages feed and start building
binariers for them again.
The current status of "oldpackages" is this:
If you are using trunk and want to use the possibly outdated packages
you have to enable the oldpackages feed and build them manually.
For that copy feeds.conf.default to feeds.conf, open it with an editor and remove the # in front of "src-git oldpackages ...".
Then do: "./scripts/feeds update oldpackages && ./scripts/feeds install -a -p oldpackages"
and they will reappear in make menuconfig.
If you are using barrier breaker in the final version we will still
build these outdated packages in binary form but won't enable the
package repository in opkg.conf by default, so you have to manually
opt-in to use these packages by uncommenting the respective line for oldpackages in /etc/opkg.conf
The next release after barrier breaker will not include
any unmaintained binary packages at all not even as opt-in.
So if you want to see some of the old packages reappearing in trunk and
future releases please adopt them and become a maintainer or convince
someone else to do it. See
https://github.com/openwrt/packages/blo … IBUTING.md