CVS Modules for Windows Build

Hey folks! I just updated my highly-detailed build instructions to use
SVN (see <http://cleardefinition.com/page/Windows_Build_Instructions/>
). There are a few extra modules that are used (but not as far as I can
tell updated) with the builds, and it seems we have been tagging (at
least some of) them for each release. How do we plan on handling these
in the future? Should/will they be migrated to SVN, left untagged in
CVS, or some other solution (perhaps installed as mingw dependency like
libiconv and expat in 2.5)?

The modules are as follows - starred ones are listed as being checked
out under a release tag/branch in my instructions:
For 2.5 and 2.4:
libpng*
popt*
fribidi

For 2.4 only:
libiconv
expat

Thanks again for the opportunity to work on AbiWord during the Summer of
Code - I'm gearing up and can't wait to really get into it full time!

Ryan
Received on Sat May 26 20:55:49 2007