The startup instructions to point to an alternate database directory or maybe keep this database in memory, as I discover is possible (which is ok for a test), to avoid any conflicts with existing installations, would be interesting pieces of info to add to the guide.
If you assumed I created an installer. Not so.
I did not create an installer, and then go on to install the build in Windows as standard., in which case it would have been advisable to install in a separate directory. But this does not apply. Explanations below.
It’s right there in the instructions :
“If you are in a hurry you can now run darktable by executing the darktable.exe found in the build/bin folder, install in /opt/darktable as described earlier, or create an install image”
I ran the executable from the /opt/darktable directory - exactly as instructed, so it was not possible that I had created any mixups with my prior 3.4 version, which was installed from the binary distribution as many users on Windows, would so do.
I do also hope you can accept that, any set of instructions, like the build for Windows which I followed, might make certain assumptions of the skill level of the end user. When you follow a Google map, it does not need to tell you to move one foot in front of the other, or give you instructions on how to drive your car, it makes certain assumptions, that you have those elementary issues sorted.
There is value, as I have done, to point out to anyone, who might have wanted to follow those instructions, that there is a level of knowledge assumed, and if the experience has not been gained prior, there would be a learning curve. Especially as you are most likely addressing Windows users, who may have never seen a command line before.
Simple things like - add these statements to a user startup file, would leave some users pondering - how do I achieve this? I cannot assume any skill levels of those who read my comments, so it is fair that I pointed out these caveats. Nothing scary, better to let them know, there is a learning curve for some.
With my experience, I still had to figure out a few things, simple things like what kind of editors does linux use, when a unix typical “vi” command to edit files did not work. I never used linux professionally, only unix, but it was a relatively easy transition to google this and realise that in linux its now “vim” not “vi”.
I was also once a technology educator, who wrote teaching guides and taught a fair bit, so it’s valid to assert, the instructions can always be improved to assure their success. I hope it can become more accepted, on techie centric sites, to also see things from the point of view of non techies. When I have the time, and the mysteries of this build process are fully resolved, I’d love to enhance those build instructions, and make this available, and hopefully anyone, at any skill level, as long as they can type and move a mouse, will have ALL of the instructions, however elementary these are, to follow a set of instructions, that are a superset of what I attempted to follow, and have even more of an opportunity to succeed at the build.
I am glad that not all the instructions succeeded, I wish they had. Once I figure out why, it will be easier for the next person who follows suit.