Just following up the src/inkscape-version.cpp thing about revision numbering. What're we going to use instead of svn.revision? Anything? I vote that for official releases it go, but for development versions it's preferable to have it if we can in any way.
(Don't jump on me, it's an innocent suggestion :P)
I've also been wondering about whether a Python build system mightn't be better in some ways for some things, especially since Bazaar is Python software and you might be able to get better integration with it there. I've not decided yet whether I'm planning on doing my Win32 packaging step for generating the Win32 installer in Python or NSIS, there are pros and cons both ways (I do intend to do it though). I think NSIS currently has the upper hand.
As we've released this is when we were planning on moving to Bazaar. I
currently don't have that perfectly the way that I want.
Basically, because we have the webpage and everything in SVN, the Bazaar
import pulls all of that into the repository. This makes the repository
larger than it needs to be. I can pull out trunk, but then I loose the
branch associations with the various branches we've made off of trunk.
I've got a few things left to try that the Bazaar team has suggested.
If it takes more than a day or two, I'll just upload the full
repository. I think that making it smaller is an optimization worth
trying for, but not a requirement. I just wanted to tell people where I
am on it.
--Ted
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel