History of Coding - Pass 1
<p>Always a good starting point, simply pull the base repository to a blank directory. In this case I've renamed the original /srv/website/bitweaver and am sitting at a command prompt in /srv/website.</p>
<pre>
git clone git@github.com:lsces/bitweaver.git</pre>
<p>This starting point links to a number of submodules so the next step is to clone them as well. So one drops down into the main bitweaver directory and run.</p>
<pre>
git submodule update --init --recursive</pre>
<p>A number of things failed here starting with references to missing entries in the .gitmodules file, but I could not initially work out where the problem was. Then I spotted that the new bitweaver directory had subdirectories for packages I did not plan to worry about initially. So the next step was to cull those entries for the time being.</p>
<pre>
git rm -r --cached config/externals/smarty
rm -r config/externals/smarty</pre>
<p>And this continued to remove all the secondary stuff I did not want to have to worry about yet. Many may be added back later. Once tidied, this needs pushing to github</p>
<pre>
git commit -m "Remove unwanted directories and update .gitmodules"
git push origin master</pre>
<p>Then the submodule init command can be repeated ... and the next set of directories sorted. I did come unstuck with the kernel/adodb folder as this is not in bitweaver, it was part of the kernel repository and so I needed to decent into that and repeat the process on just 'adodb'. Not sure why all of this is needed but one has to update the submodule and then the wrapper.</p>
<pre>
git add .
git rm -r --cached adodb
rm -rf adodb
git commit -m "Remove adodb directory from kernel submodule"
git push origin master
cd ..
git add .
git commit -m "Update kernel submodule to remove adodb directory"
git push origin master
</pre>
<p>Once completed the submodule init command ran clean and everything seems to be in the right place. At least that is where I am at this moment while I try and decide on the next step. I think I need a branch on lsces/bitweaver and then build the new fork on that branch?</p>
<pre>
git clone git@github.com:lsces/bitweaver.git</pre>
<p>This starting point links to a number of submodules so the next step is to clone them as well. So one drops down into the main bitweaver directory and run.</p>
<pre>
git submodule update --init --recursive</pre>
<p>A number of things failed here starting with references to missing entries in the .gitmodules file, but I could not initially work out where the problem was. Then I spotted that the new bitweaver directory had subdirectories for packages I did not plan to worry about initially. So the next step was to cull those entries for the time being.</p>
<pre>
git rm -r --cached config/externals/smarty
rm -r config/externals/smarty</pre>
<p>And this continued to remove all the secondary stuff I did not want to have to worry about yet. Many may be added back later. Once tidied, this needs pushing to github</p>
<pre>
git commit -m "Remove unwanted directories and update .gitmodules"
git push origin master</pre>
<p>Then the submodule init command can be repeated ... and the next set of directories sorted. I did come unstuck with the kernel/adodb folder as this is not in bitweaver, it was part of the kernel repository and so I needed to decent into that and repeat the process on just 'adodb'. Not sure why all of this is needed but one has to update the submodule and then the wrapper.</p>
<pre>
git add .
git rm -r --cached adodb
rm -rf adodb
git commit -m "Remove adodb directory from kernel submodule"
git push origin master
cd ..
git add .
git commit -m "Update kernel submodule to remove adodb directory"
git push origin master
</pre>
<p>Once completed the submodule init command ran clean and everything seems to be in the right place. At least that is where I am at this moment while I try and decide on the next step. I think I need a branch on lsces/bitweaver and then build the new fork on that branch?</p>