On Mo, 2002-12-30 at 21:40, Beman Dawes wrote: > We can't change CVS, so we have to deal with its oddities.
Since generated documentation structure usually reflects structure of the software, even a little change in, for example, class interface or hierarchy could produce a huge change in documentation such as adding, removing, renaming generated html (xml? texinfo?) files, which is something the cvs is not well suited for. I suggest not to use current boost cvs module for generated documentation, but create a separate module instead. There are several reason for that: - keep main cvs tree small, generated doc are usually huge - documentation usually stays a little behind actual code, so having it in code tree brings little benefit - it's possible to make a separate sf release of a module, releasing doc more often then library is practical, even releasing a new doc for old stable library version - it's easier for cvs users, who sync often and don't need/want huge binary file (pdf?) update over modem dial-up every day - for versioned doc releases, other people are encouraged to contribute unusual or exotic formats or translations back to project - somebody is perfectly happy to build the doc himself Petr Kocmid ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
