<div dir="ltr">Hi Ryan,<div><br></div><div>The +testing variant of revision 2 is equivalent to no variant at revision 1. So, yes it does have an effect, of removing quite a lot of installed files that are unnecessary except for when testing.</div><div><br></div><div>David</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jun 11, 2016 at 3:21 AM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On Jun 10, 2016, at 12:31 PM, <a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a> wrote:<br>
><br>
> Revision<br>
> 149308<br>
> Author<br>
> <a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a><br>
> Date<br>
> 2016-06-10 10:31:56 -0700 (Fri, 10 Jun 2016)<br>
> Log Message<br>
><br>
> paraview: Previous commit (because of +testing) should have increased revision.<br>
<br>
> --- trunk/dports/science/paraview/Portfile 2016-06-10 15:00:52 UTC (rev 149307)<br>
> +++ trunk/dports/science/paraview/Portfile 2016-06-10 17:31:56 UTC (rev 149308)<br>
> @@ -9,7 +9,7 @@<br>
><br>
> name paraview<br>
> version 5.0.1<br>
> -revision 1<br>
> +revision 2<br>
<br>
Since the +testing variant added by the previous commit was not a default variant, forcing users to rebuild will do nothing; the revision should not have been increased (but don't change it back now).<br>
<br>
<br>
</blockquote></div><br></div>