Wednesday 27 of August, 2025

Ignoring all the time wasted this morning on chasing the tax refund ( See the rants blog ), I actually had a quite successful morning on the code base. I had been getting my knickers in a twist partially because I was trying to shortcut some of the process and as a result my own code base was being corrupted. Today I started with a clean sheet, and initially cloned the lsces/bitweaver repository to an empty file. THEN I sorted out just what submodules I actually needed and with a combination of edits to .gitmodules and the actual directory tree I got to a place where I have a clean base to work off. That it will not actually run on PHP8.4 is not relevant. It is that it is a stable view of the old code into which I can now commit my own changes in my own forks of that code. I'm just working out what the next step should be and I think I need to create a PHP8.4 branch from which I can develop the new code.

I've had to jump through a few hoops while getting used to git and I DO need to document all that, starting with simply setting up authentication into my repositories. One of the tidies to the .gitmodule file was to replace https:// links with git@ SSH links but I think I have all this under control now.

During all of the playing around I have actually committed all the material for a package and pushed it to github, the only problem was it appeared in the bitweaver/ilike repository rather than my lsces/search one. Fortunately deleting it was fairly easy. I am learning the git methods from scratch as previously I had always used mercurial for code management with a mirror into the github version of a repository. Eclipse handled all of that fairly transparently so now I need to work out what the equivalent interface is from VSCode into raw git. I can see file handling via staging, but moving forward it would be nice to commit partial changes across a set of files which was natural in eclipse. The starting point however is all the hoops I passed in building the current base.