On Mon, Feb 4, 2013 at 2:24 PM, Ryan Schmidt <[email protected]> wrote: > > On Feb 4, 2013, at 11:12, [email protected] wrote: > >> Revision: 102500 >> https://trac.macports.org/changeset/102500 >> Author: [email protected] >> Date: 2013-02-04 09:12:42 -0800 (Mon, 04 Feb 2013) >> Log Message: >> ----------- >> mercurial-devel: add subport to mercurial >> >> Modified Paths: >> -------------- >> trunk/dports/devel/mercurial/Portfile >> >> Modified: trunk/dports/devel/mercurial/Portfile >> =================================================================== >> --- trunk/dports/devel/mercurial/Portfile 2013-02-04 17:12:34 UTC (rev >> 102499) >> +++ trunk/dports/devel/mercurial/Portfile 2013-02-04 17:12:42 UTC (rev >> 102500) >> @@ -34,6 +34,15 @@ >> >> python.default_version 27 >> >> +subport mercurial-devel { >> + bitbucket.setup mirror mercurial-crew e71c2ff93167 >> + name mercurial-devel >> + version 2.5.0.99 >> + >> + checksums rmd160 e76616497368cfa6808a1749d98670bc0dbf48a0 \ >> + sha256 >> b56fac24102d616dea1b606f66131b347016717357af1257b538cb869749b89f >> +} > > The mercurial and mercurial-devel ports should presumably conflict with one > another.
Yes, good catch. I'll update these in a little bit. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
