Boost logo

Boost :

Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2012-12-11 09:29:31

> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]] On Behalf Of Beman
> Dawes
> Sent: Friday, December 07, 2012 4:55 PM
> To: Boost Developers List
> Subject: [boost] [Git] Documentation for Git and Modular Boost conversion
> We are starting to pull together documentation for the Git and Modular Boost conversion.
> Comments and corrections welcome!

* GitHub.? exercise? and other links are broken?

* Layout of directory structure seems a significantly different structure to most Boost libraries,
with boost_1-0-99/boost and boost_1-0-99/libs (as referenced Is this intended?

* Where do example and doc (and build and src go)?

* Surely no library project (however simple) should exist without /doc and /example (and /test)

* The output from any non-trivial library will be better sent to a log file - and even simple ones
that don't work as expected are better attached to a "help!" message than pasted suffering
end-of-line mutilation by the mail program.

* "Hint: (((git help command-name}}}... " does look right? A TODO?

* Has anyone actually used these instructions yet?
(Some previous Boost instructions didn't actually work if you followed them blindly :-(

* These instructions don't guide a user with an IDE Visual Studio, NetBeans, Eclipse ... on how to
set up their project so that it can be easily transferred from (and to) the development tool.

* Nor do they deal with the most common case of people moving sandbox SVN projects to git. Or will
this be done automatically? (Some might be pruned as obsolete/abandoned?



Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
+44 1539 561830  07714330204

Boost list run by bdawes at, gregod at, cpdaniel at, john at