Re: [OE-core] opkg pkg_prerm on package update

2016-01-25 Thread Burton, Ross
On 25 January 2016 at 18:04, Andreas Müller wrote: > As you know of "i'm being deleted" or "i'm being upgraded" - you have > a pointer for this? To find a common solution: Do package managers > share same behaviour here - or is there a common document package > managers should comply with? > The

Re: [OE-core] opkg pkg_prerm on package update

2016-01-25 Thread Andreas Müller
On Mon, Jan 25, 2016 at 6:37 PM, Burton, Ross wrote: > > On 22 January 2016 at 09:50, Andreas Müller > wrote: >> >> although opkg 0.2 -> 0.3 is long ago I noticed a change in behaviour >> when updating a package: >> >> * 0.2.x did not call pkg_prerm >> * 0.3.x calls pkg_prerm >> >> Is calling pkg

Re: [OE-core] opkg pkg_prerm on package update

2016-01-25 Thread Burton, Ross
On 22 January 2016 at 09:50, Andreas Müller wrote: > although opkg 0.2 -> 0.3 is long ago I noticed a change in behaviour > when updating a package: > > * 0.2.x did not call pkg_prerm > * 0.3.x calls pkg_prerm > > Is calling pkg_prerm a valid behaviour when updating a package? > opkg is copying

[OE-core] opkg pkg_prerm on package update

2016-01-22 Thread Andreas Müller
Hi, although opkg 0.2 -> 0.3 is long ago I noticed a change in behaviour when updating a package: * 0.2.x did not call pkg_prerm * 0.3.x calls pkg_prerm Is calling pkg_prerm a valid behaviour when updating a package? Why I ask this: systemd.bbclass does * stop a service on pkg_prerm * restart