On 13/08/14 14:02, Steven Barth wrote:
What you see right now in RC3 will be there in the final as well, it
will just be split up into subdirectories and the unmaintained packages
"oldpackages" need to be manually enabled in /etc/opkg.conf on your
router before being installable using opkg.
So, are these lines gonna be valid in opkg.conf ?
src/gz base
http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/base
src/gz luci
http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/luci
src/gz management
http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/management
src/gz packages
http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/packages
src/gz routing
http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/routing
src/gz telephony
http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/telephony
Thanks!
In RC3 they are still all
together in one package repository.
There might be a few more packages in the final but what is in RC3 now
(rsync is still running btw.) is a pretty good estimate of what will be
there.
Cheers,
Steven
Am 13.08.2014 um 12:46 schrieb Aaron Z:
On Wed, Aug 13, 2014 at 4:13 AM, Steven Barth <cy...@openwrt.org> wrote:
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.
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. Some packages there might be broken due to changes in
the
SDK but this will hopefully get addressed before the final release.
The next
release after barrier breaker will not include any unmaintained
packages at
all not even as opt-in.
So, are the precompiled packages on openwrt.org [1] indicative of what
will be available for the final release of BB?
From there on ar71xx, nano was missing from RC1, but is back for RC2
[2] and RC3 [3].
Looking in the same folder [1] for the packages that Valent mentioned
in his second ticket, I also see bluez-libs [4], bluez-utils [5],
/i2c-tools [6], ntpclient [7], picocom [8] and python [9] as
precompiled packages.
Will those still be available in the final release?
[1]
http://downloads.openwrt.org/barrier_breaker/14.07-rc2/ar71xx/generic/packages/
[2]
http://downloads.openwrt.org/barrier_breaker/14.07-rc2/ar71xx/generic/packages/nano_2.3.6-1_ar71xx.ipk
[3]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/nano_2.3.6-1_ar71xx.ipk
[4]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/bluez-libs_3.36-3_ar71xx.ipk
[5]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/bluez-utils_3.36-12_ar71xx.ipk
[6]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/i2c-tools_2013-12-15-1_ar71xx.ipk
[7]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/ntpclient_2007_365-4_ar71xx.ipk
[8]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/picocom_1.7-1_ar71xx.ipk
[9]
http://downloads.openwrt.org/barrier_breaker/14.07-rc3/ar71xx/generic/packages/python_2.7.3-2_ar71xx.ipk
Aaron Z
A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects.
— Robert Heinlein, Time Enough for Love
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
