On 22 January 2016 at 09:50, Andreas Müller <schnitzelt...@googlemail.com> 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 what dpkg does [1], which makes sense considering opkg is basically a dpkg clone. It passes variables to the script so you can identify if the context is "i'm being deleted" or "i'm being upgraded". This changed in http://git.yoctoproject.org/cgit/cgit.cgi/opkg/commit/?id=a8555d352d2851ee1482b74b57ba9eacfb354c18 if you want more context. [1] https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html is what dpkg does, fwiw. Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
