Hi, you could fork the cctbx_project into your personal github account,
then check out the forked repository locally. Make the changes to support
Fedora and push them back as commits to your forked repository. Then, make
a local edit to bootstrap.py to pull from your repository. Something like
this (lines 755-757):
# Core CCTBX repositories
# These must all provide anonymous access.
class cctbx_module(SourceModule):
module = 'cctbx_project'
anonymous = ['git',
'[email protected]:cctbx-xfel/cctbx_project.git',
'https://github.com/cctbx-xfel/cctbx_project.git',
'
https://github.com/cctbx-xfel/cctbx_project/archive/master.zip']
(as seen in this commit)
https://github.com/cctbx-xfel/cctbx_project/commit/df22c2f4fa60f484e0ec3f115...
You can use that edited bootstrap to test your changes.
Does that make sense? When you are done, you can push the changes back
using a pull request from your forked repository.
-Aaron and Billy
On Thu, Dec 14, 2017 at 4:15 PM, Luc Bourhis
Hi,
I have found a few issues with auto build on recent versions of Fedora. I need to edit files in libtbx/autobuild to fix them but then I want to test that running bootstrap works. But then bootstrap.py always pull from github. I don’t want to push my changes to github until it’s solid though. How do you guys approach that?
Best wishes,
Luc
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb