<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 2 December 2014 at 09:46, Thomas Goirand <span dir="ltr"><<a href="mailto:zigo@debian.org" target="_blank">zigo@debian.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">if [ "$1" = "configure" ] ; then<br>
    <some-other-stuff><br>
    /usr/share/openstack-dashboard/manage.py compress --force<br>
    <some-other-stuff><br>
fi<br>
<span class="">if [ "$1" = "triggered" ] ; then<br>
    /usr/share/openstack-dashboard/manage.py compress --force<br>
fi<br>
<br>
</span>Is it *that* simple? I'm surprised by the "interest" thing just being<br>
hinted with a directory. Does this mean that if anything changes in that<br>
directory, then there's a trigger, and the openstack-dashboard compress<br>
stuff will happen?<br></blockquote><div><br></div><div>There might be times when compress is run twice.  e.g. when upgrading openstack-dashboard and /usr/share/javascript/jsencrypt at the same time.</div><div><br></div><div>However I cannot think of anyway to fix this in a way that doesn't create other problems. So this might actually be the best solution.</div><div><br></div><div>(e.g. you could explicitly raise the trigger inside the configure event, however that will trigger all applications that have an interest in /usr/share/javascript/jsencrypt which is probably not desirable)</div></div>-- <br><div class="gmail_signature">Brian May <<a href="mailto:brian@microcomaustralia.com.au" target="_blank">brian@microcomaustralia.com.au</a>></div>
</div></div>