On Jul 30, 2008, at 23:26, Blair Zajac wrote: > Ryan Schmidt wrote: > >> On Jul 30, 2008, at 12:50, [EMAIL PROTECTED] wrote: >> >>> Revision: 38761 >>> http://trac.macosforge.org/projects/macports/changeset/ >>> 38761 >>> Author: [EMAIL PROTECTED] >>> Date: 2008-07-30 10:50:38 -0700 (Wed, 30 Jul 2008) >>> Log Message: >>> ----------- >>> Add profiling variant (mostly of interest to those working to >>> improve darcs internals). >> >> FYI, when you add a variant, you don't need to increase the port >> revision, since nothing will change for those users who already had >> the port installed. > > But on the other hand, if you weren't aware of this variant, there > would be no > way to tell. With a bump in revision, you can check for new variants.
I don't like increasing the revision as a means for informing users that a new variant is available. Increasing the revision causes the port to show up in "port outdated" and on the mailing list and hopefully in the Guide, users are encouraged to update their ports. For some larger ports and/or slower computers this can take a long time. Let's not waste users' time by needlessly increasing port revisions when nothing about the files that get installed has changed. I think it's a fine idea to have a way to inform users that new variants are available for ports they have installed. But let's make a new way for users to be informed of that. Let's not overload the port revision. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev