I didn't realise people were following oe-core master on deployments of a few
thousand systems! This is definitely a use-case for the stable branches.
In that case I have some interesting information for you. OpenPLi also
follows 'master' (because for many things we need the bleeding edge new
On 07/02/15 22:55, Paul Barker wrote:
> I didn't realise people were following oe-core master on deployments of a few
> thousand systems! This is definitely a use-case for the stable branches.
The deployed systems are currently on:
opkg mips32el 1:0.2.2-r0
opkg-collateral mips32el 1.0-r2
opkg-con
On Sat, Feb 07, 2015 at 09:47:32PM +1100, Peter Urbanec wrote:
> On 17/01/15 09:15, Paul Barker wrote:
> > All these changes work locally in qemuarm and the on-target upgrade
> > path is
> > mostly clean. opkg-collateral does get left behind on the target
> > filesystem
> > after a
On 17/01/15 09:15, Paul Barker wrote:
> All these changes work locally in qemuarm and the on-target upgrade path
> is
> mostly clean. opkg-collateral does get left behind on the target
> filesystem
> after an upgrade but it's effectively an empty package. I don't think
> this
>
