[cctbxbb] Not wishing to raise this again but...

[markus.gerstel at diamond.ac.uk]

Hi,

I'm don't really mind whether we do submodules or not, as long as bootstrap will be able to deal with older git versions that do not support submodules. If we got the development history of these modules, say ccp4io, I would be happy to convert them to git, too.
It forms part of a larger debate if we want to merge modules such as ccp4io into the cctbx repository, or break them apart - for example I suspect eg. xfel could move into a separate repository. Again I can offer to merge the histories and/or separate projects. But these decisions are above my paygrade.

-Markus



-----Original Message-----
From: cctbxbb-bounces at phenix-online.org [mailto:cctbxbb-bounces at phenix-online.org] On Behalf Of Luc Bourhis
Sent: 16 June 2016 12:29
To: cctbx mailing list
Subject: Re: [cctbxbb] Not wishing to raise this again but...


> On 16 Jun 2016, at 13:16, Marcin Wojdyr <wojdyr at gmail.com> wrote:
> 
>> As for boost, SCons and ccp4io, I guess you propose to just 
>> incorporate their whole directory tree in one single commit
> 
> I don't have an opinion here. Submodule are fine. Do you mean making 
> git repositories for these three projects and adding them as 
> submodules?

Boost has already an official git repository but SCons does not.  So for SCons, the git submodule solution would indeed require creating git repositories. What about ccp4io? There is no official git repo, is there?

Just to make it clear what I meant with “one single commit”: copy the whole SCons directory at the top of the cctbx hierarchy, then “git add scons” and then “git commit”.


_______________________________________________
cctbxbb mailing list
cctbxbb at phenix-online.org
http://phenix-online.org/mailman/listinfo/cctbxbb

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom