Re: [boost] Creating a new(-ish) library in modular boost ?

Subject: Re: [boost] Creating a new(-ish) library in modular boost ?
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2014-03-26 13:38:11

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Edward Diener
> Sent: 20 March 2014 17:56
> To: boost_at_[hidden]
> Subject: Re: [boost] Creating a new(-ish) library in modular boost ?
> 
> On 3/20/2014 1:07 PM, Paul A. Bristow wrote:
> > I have fumbled (and stumbled) trying to create a
> > revised-possibly-to-be-proposed for Boost library in the new modular boost
> format.
> >
> > So far I have created a folder /modular-boost/svg_plot
> >
> > And copied all the files into it in the new modular format and got the
> > library working OK (compiling, tests, examples, docs etc).

> > Can anyone suggest what sequence of actions I should take to set this up?
> 
> The easiest way I found is to setup a GitHub repository under your GitHub
account.
> Then clone that empty repository to your local modular-boost/libs. Add all
your files
> to the local repository. Commit everything. Then push everything back to your
> GitHub remote ( origin/master ).
> 
> Later if you like you can create a local 'develop', merge your local 'master'
to
> 'develop', then push your local 'develop' to 'origin/develop' on GitHub. The
you can
> do the usual changes and testing on 'develop' before you merge your 'develop'
> changes back to 'master'.

These suggestions proved successful in my case.

I had to move my library files to a backup location (and abandon the existing
.git file) before following your procedure above.

If I had wanted to keep my full history, it would have been better to start work
on the new library with a GitHub repository as you suggest. (Of course, if you
are using a free account, all work that you push will be visible, warts and all
;-)

(Some GitGuru may be able to suggest how better to do it?).

Thanks

Paul

Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone] 07714330204