[wpkg-users] removing a package dependency has uninstalled that first package from all clients and then reinstalled

[Stefan Pendl]

Am 30.11.2016 um 23:22 schrieb Rainer Meier:
> Hi Paul,
>
> I think you pretty much hit the worst case scenario about dependency
> changes but WPKG will make sure you end up in a consistent state
> (assuming all your packages uninstall/install properly).
>

You can easily avoid this by using neutral packages to resolve dependencies.

For example, I do have a package Java, which is currently including 
JRE8u111, but was including JRE6unnn and JRE7unnn previously.

All other packages depending on JRE are depending on the package Java, 
so when I replaced JRE6 by JRE7 by JRE8 there was nothing removed.

<!-- code start (watch for line wraps) -->
<package id="Java" name="Java" revision="2014.10.04" reboot="false"
     priority="10" execute="once">

     <include package-id="JRE6" os="5\.0\.\d{4}"/>
     <include package-id="JRE8">
         <condition>
             <check type="logical" condition="not">
                 <check type="host" condition="os" value="5\.0\.\d{4}"/>
             </check>
         </condition>
     </include>
</package>
<!-- code end -->

-- 
*Stefan P.*

Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?