On 2015-3-11 03:43 , Mojca Miklavec wrote: > On Tue, Mar 10, 2015 at 4:43 PM, Andrea D'Amore <[email protected]> > wrote: >> On 10 March 2015 at 13:50, Ryan Schmidt <[email protected]> wrote: >>> For future reference, since this does not change the way that the port >>> installs by default, the revision should not have been increased. >> >> I stood by the rule to bump revision if installed files changed, >> regardless if the change affected default install or not. >> This actually makes more sense, duly noted. > > Even if the new variant would become default, there would be no need > for a revbump. The criteria is that files change, but the package > signature doesn't.
That's a little more arguable. You're right that any existing archives are still valid. But if the new default variant adds important functionality, you may want to rev bump so that users get it right away. - Josh _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
