Hi everyone! On Sat, Feb 18, 2017 at 08:10:22AM +0000, Kevin Darbyshire-Bryant wrote: > > On 18 Feb 2017, at 00:06, daniel <dan...@dd-wrt.com> wrote: > > > > And I also do not want opkg to invoke the init scripts of the just upgraded > > packages until I have finished all my checks and stuff. > > > > I thought it might be useful for others too, if opkg has this option that > > let > > you control the upgrade process a bit more. > > I think this is a useful tweak for very little code increase. I was > working on my own patches for dnsmasq the other day and found the > opkg install 'copying & auto starting' behaviour annoying as it > (initially) confused my testing.
I bumped into this submission while browsing through patchwork and it partially solves another problem I have: The need to generate images using the ImageBuilder which do have certain packages installed with their init scripts being disabled (uci-defaults and the rest of default-postinst should be processed in that cause though)... I went on and simply set an environment variable which can be checked for in the postinst script which inherits it. In that way I didn't need to patch opkg. Could such a solution be helpful to you as well? Because if so, that would simply be a matter of convention, similar to PKG_UPGRADE (see package/base-files/files/lib/functions.sh) > > > > > What do you think ? > >> On 02/17/2017 06:17 AM, Jonas Gorski wrote: > >> Hi, > >> > >>> On 16 February 2017 at 02:14, Daniel Danzberger <dan...@dd-wrt.com> wrote: > >>> Calling opkg <cmd> with --no-configure prevents opkg > >>> from running the configuration of the package (postinstall scripts ..etc) > >>> > >>> This way opkg will only install the package, without restarting the > >>> service for example. > >> > >> What's the use case for this? When would I want to do that? > >> > >>> Signed-off-by: Daniel Danzberger <dan...@dd-wrt.com> > >> > >> > >> Regards > >> Jonas > >> > > > > -- > > Regards > > > > Daniel Danzberger > > embeDD GmbH, Breitenweg 10, CH-6370 Stans > > > > _______________________________________________ > > Lede-dev mailing list > > Lede-dev@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/lede-dev > > _______________________________________________ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
