[OE-core] opkg in svn?

[Richard Purdie]

Hi Paul,

Looking at opkg, I did have one other question. Currently in most builds
we build opkg (either as the package manager or at least for
update-alternatives). opkg is in svn but its one of the few remaining
components we use from svn. It means we have to build subversion-native
which has a fairly long dependency chain. It would be nice if we didn't
need to so is there any chance we can move opkg to git?

An alternative would be to have good tarball releases we could use
instead?

FWIW, in OE-Core we currently have:

recipes-devtools/installer/adt-installer_1.0.bb~:SRC_URI = "svn://opkg.googlecode.com/svn;module=trunk;protocol=http \
recipes-devtools/installer/adt-installer_1.0.bb:SRC_URI = "svn://opkg.googlecode.com/svn;module=trunk;protocol=http \
recipes-devtools/opkg/opkg_svn.bb:SRC_URI = "svn://opkg.googlecode.com/svn;module=trunk;protocol=http \
recipes-devtools/ubootchart/ubootchart_svn.bb:SRC_URI = "svn://ubootchart.googlecode.com/svn/;protocol=http;module=trunk \
recipes-multimedia/tremor/tremor_20120314.bb:SRC_URI = "svn://svn.xiph.org/trunk;module=Tremor;rev=18221;protocol=http \
recipes-sato/puzzles/puzzles_r9765.bb:SRC_URI = "svn://svn.tartarus.org/sgt;module=puzzles;rev=${MOD_PV}"

so opkg is three of the remaining six svn references and is by far the
most significant factor in builds.

Cheers,

Richard