On 25/02/2010 09:33, Zachary wrote: > Hey everybody, > With the rise in popularity of various forks for new platforms (andriod, > iphone os, maemo, etc) > I'd like to see that they don't get lost over time and splinter off beyond > usefulness. > > I'm already having a hard time keeping track of them, and I'd really like to > give them the home they deserve. > But I want to know what you think first. > > Is it worth pursuing these forks and giving them svn (Separate repo from the > main ioquake3 svn)? > What else do you want to see? > -Zachary
To carefully merge all that stuff back into the main tree, so that all platforms could be built from a single source would be the most awesome thing, I think. Unfortunately that is bound to take a lot of work and care to be done properly. I already shiver at the impact of supporting Win64. Any other approach, though, would in my opinion lead to it diverging over time and sooner or later render it useless. It's difficult enough to fix bugs in a single tree. Imaging tracking and individually patching them for every single mobile platform separately! Things might go a different way, if there was a maintainer for each mobile platform, with the sole responsibility of monitoring all changes to the main ioquake3 source tree and carefully merging them all into the source tree for the assigned mobile platform. But this approach requires people with real dedication to the platform (much like the way I am dedicated to FreeBSD). If none of these things can be achieved, having the code in SVN would at least provide the world with a historical record of these achievements. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? _______________________________________________ ioquake3 mailing list [email protected] http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
