Re: Question regarding Boost Documentation

From: René Ferdinand Rivera Morell (grafikrobot_at_[hidden])
Date: 2024-08-10 00:35:28

On Fri, Aug 9, 2024 at 3:55 PM Robert Ramey via Boost
<boost_at_[hidden]> wrote:
>
> On 8/7/24 9:07 PM, René Ferdinand Rivera Morell via Boost wrote:
> > On Wed, Aug 7, 2024 at 10:48 PM Robert Ramey via Boost
>
> > Not checking in the generated docs to git relieves all the other Boost
> > authors from downloading your documentation with every pull.
>
> Hmmm - but it doesn't transfer any files which haven't been changed?
>
> But no matter.  Here is what I would like to be able to do and I think
> lots of library users would also.
>
> a) Find a library I want to use, fix, enhance, inspect, try out, or
> whatever.
>
> b) download the library via github clone.
>
> c) find one my machine all the source, notes, documentation, examples,
> tests, etc that I need to use/evaluate the library.
>
> d) Once I've done the above, I would like to be able to just use the
> library on my local machine without necessarily being connected to the
> net. I don't want to have to build anything, install more tools or whatever.
>
> e) If I feel the need to be sure that the docs are current, I do the
> same thing I would with source, headers, etc. ... do a git pull
>
> f) I would also like to continue to browse all the documentation for all
> the libraries through an index on the web site - just as we do now.
>
> g) If I make a change in the documentation I would handle it just as I
> do for code - push the changes.
>
> Does this sound so unreasonable?

Sounds reasonable. I already do that. I also test any examples
included in the documentation, automatically. I don't understand your
problem.

-- 
-- René Ferdinand Rivera Morell
-- Don't Assume Anything  -- No Supone Nada
-- Robot Dreams - http://robot-dreams.net