Hamish wrote: > > r33944 | hamish | 2008-10-21 03:35:40 +0100 (Tue, 21 Oct 2008) | 1 line > > remove code based on Vask_lib+Xmons; porting will happen in > > develbranch6 then when operational be merged back into grass7 SVN > > > > Isn't this backwards? > > > > There's no need for i.ortho.photo to change in 6.4, as monitors (and > > the display architecture generally) won't be changing there. > > it's just easier to incrementally test with an otherwise working suite. > i.e. the config file setup modules will be pretty easy to fix, while the > two i.points clones may take much longer. > > I had thought about leaving i.ortho.photo/libes/ in trunk, as that has > some hope of being reused (ie all but ask_camera.c to be merged into > lib/imagery/). My primary motivation was that porting fixes between two > active branches seemed like a nightmare.
It probably will be a nightmare. Which is why I would suggest not bothering with 6.4. Anything done there will have a rather limited life expectancy, and may not actually help all that much for 7.0. I suspect that the "incremental" approach will be more trouble than it's worth, i.e. you'll end up repeatedly writing code then discarding it. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
