Re: HTML version of documentation - Store using SVN or leave users to build

"Paul A. Bristow" <[email protected]>
Newsgroups gmane.comp.lib.boost.documentation
Message-ID <[email protected]>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Daniel James
> Sent: Wednesday, September 07, 2011 10:46 AM
> To: Discussion of Boost Documentation
> Subject: Re: [Boost-docs] HTML version of documentation - Store using SVN or leave users to build
> 
> On 7 September 2011 10:02, Paul A. Bristow >
> >
> > But that doesn't answer the need for people to be able to read the
> > html without generating it themselves (requiring Quickbook, Doxygen
> > Autoindex, bjam ...)
> 
> Can't you just upload them to a web server and include them in the zipfile? I think sourceforge,
github and
> bitbucket all have free static hosting for open source projects. You could ask to be added to the
boost-
> sandbox sourceforge project, although github and bitbucket look easier to setup. For sourceforge
you
> need to set up ssh keys and rsync, which is a bit of a pain.

Well I noted that many people seemed to be doing something like that, but it seemed a most untidy
solution, when the main project files are in Boost-sandbox.  And a hassle, for the author and
readers?
 
> By the way, when building doxygen/boostbook based documentation, you should delete the previously
> generated html files as the names aren't consistent so you end up with duplicates.

Indeed a hazard, as I have already discovered.

Would a zip of the html docs be better?

Just trying to find the 'right' thing to do.

Paul

---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
+44 1539 561830  07714330204
[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.