On Jan 16, 2012, at 6:28 PM, Mark Brethen wrote: > Right now, svn is necessary for testing the developer's mac-specific changes > to his code. It sounds like I should just not submit the port until the > changes are implemented into a tarball at the developer's sourceforge site.
I think the point that Ryan was making was that you can create a tarball out of the svn checkout (and even automate it so it's not much effort)... I would say that it makes sense for you to have a version of the portfile for your own testing if it's useful for you (but that the kinds of optimizations you're trying to make with svn support aren't going to be things that are already in base/) - but that if you want to create something generally useful, spending some time thinking about how you can get tarballs is worth the effort. -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
