Re: Docs in release tarballs

From: Sam Darwin (samuel.d.darwin_at_[hidden])
Date: 2024-06-06 21:56:09

The current release processes are designed to generate full archives, and
it is convenient to keep this as one of potentially many build options.
They are permanent archive records of a complete boost release.   They can
be deployed on the website, as-is.   Scripts don't need to change.    Any
long-time boost users who might expect this choice, may still access it,
the same as before.  The explanation is clear to advertise: full downloads.

The next choice: minimal, fast, source-only.    This may become the new
default "source-only".    A question is whether test/ and example/ should
also be removed.    I did try compiling this, and it appeared to succeed.
 The result was around 25% of the previous size.   That's quite an
improvement.

If both of the above choices exist, and are available as releases
(source-only, and full), then this may be the sweet spot of complexity.
 It answer the needs of basically everyone, while only requiring one
additional bundle.

On Thu, Jun 6, 2024 at 2:46 PM Andrey Semashev via Boost <
boost_at_[hidden]> wrote:

> On 6/6/24 20:26, Vinnie Falco wrote:
> > On Fri, May 24, 2024 at 2:57 PM Andrey Semashev via Boost
> > <boost_at_[hidden] <mailto:boost_at_[hidden]>> wrote:
> >
> >     Removing docs is mostly acceptable since they are available online
> >
> > Well... I don't think removing them completely is a great idea.
>
> Right, to be clear, I didn't suggest to completely remove them from
> downloads. I'm just saying that an archive without the docs would make
> sense - in addition to an archive that contains docs (whether it is a
> full package with sources or just the docs).
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>