Subject: Re: [boost] Header Inclusion practices
From: degski (degski_at_[hidden])
Date: 2017-04-12 16:16:43
On 12 April 2017 at 09:34, Robert Ramey via Boost <boost_at_[hidden]>
After considering all this, I'm thinking we should should just drop the
> zipfile distribution. The whole focus on "release" should be assign the
> magic tag to the master in github - "Release 1.63".
This seems a great idea, some time ago, on this list, I was getting dissed
for claiming that an average windows developer was able to open a developer
command prompt and lanch a boost build from there. The common opinion
seemed to be that that's not to be expected.
But now we leap to the other end, everybody should install and learn git,
notoriously obscure and alien to windows users, in order to build and use
boost! Or do you mean I should just download the snapshot zip-file on
... build and distribute the zipfiles ...
You make it sound very complicated.
> By adopting this point of view, and a couple small changes (e.g. requiring
> html documentation inside each project) we would have a "modular boost"
> which is much easier to maintain and work with.
I think the distribution of (7)-zip files, with check-sums, is the way to
fix (as in "this is it") a release.
Unless all the interdependencies between libraries are removed, I don't see
how boost can ever be modular in a meaningfull way.
-- "*Ihre sogenannte Religion wirkt bloÃ wie ein Opiat reizend, betÃ¤ubend, Schmerzen aus SchwÃ¤che stillend.*" - Novalis 1798
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk