On 18 November 2013 12:03, Richard Purdie <[email protected]> wrote: > 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? >
The answer is yes to both of these. In my queue of patches to oe-core which I'm currently testing is an update to the opkg-0.2.0, downloaded as a tarball instead of from svn. I'm also trying to organise git hosting for opkg within Yocto Project, I think I'm waiting to hear back from Michael Halstead on a couple of questions. It's just a bit slow going as I'm very busy with other work at the minute. I can send the patches I have as RFCs if someone else has time to test them - I know opkg-0.2.0 builds correctly, I just haven't had time to generate a package feed and try to do a live update of something on a real board running opkg-0.2.0. It's on my todo list but it may be a few days or weeks before I find time to test this out. -- Paul Barker Email: [email protected] http://www.paulbarker.me.uk _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
