Actually I was thinking of eventually adding non-svn support as well.... The reason I started on this project is because the version of mplayer in ports is severely out of date. When I tried to update to port I noticed that the project wants you to compile and install from svn. I also noticed a few other ports that have hacks to let the maintainers "use his/her custom scripts" stuck into the port's Makefile. I think it would be good if there was some standardized way of solving both of these problems...
On Fri, Nov 13, 2009 at 3:10 AM, Wesley Shields <w...@freebsd.org> wrote: > On Tue, Nov 10, 2009 at 10:28:17PM +0200, Eitan Adler wrote: > > Alright - I updated the wiki page to summarize the thread so far. > > I'd appreciate if people could comment on the "spec" part > > specifically. I'd like to see that section become much more specific > > (so that I could use it to unambiguously write something based off of > > it) > > > > I'm holding off on writing any new implementations at the moment to > > see where things head in terms of how things should be done. > > http://wiki.freebsd.org/EitanAdler/ports-svn > > Why only SVN? I'm not trying to be picky but if we start supporting this > for SVN it's very easy to argue we should support it for some other VCS. > Personally I think this kind of thing is best left up to the maintainer > to use his/her custom scripts and not stuff support for it into the > ports infrastructure. > > -- WXS > _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"