I know that you dislike the fact that they are optimized for 020+ because they cannot work on the Minimig.
Well, that's not really the issue I see here. what I dislike is that there is no way to tell apart original CBM binaries and these 020 binaries unless you have checksums around to compare with. My suggestion is ofcourse to alter the version strings inside the binaries as well - bump minor with 1 and set a current date, it's should be easy enough.
But then, I invite you to share your knowledge on the modded AmigaOS 3.9 you made for your Minimig (68000) so that you share it with others.
It isn't modified, the updated kickstart uses the regular ROM updates, I just put together a kickstart of my own to save RAM.
The only bits that dont work on 68000 are apps that use resource.library, and some ReAction classes (and they typically exist as 68000 compatible versions in ClassAct), some datatypes (but 3.1 works, and on such a system, how many datatypes do one need anyways?). The 3.9 Workbench works just fine, up to 45.129, where it was "optimized" for 020 (I use quotes since I _really_ cannot see _any_ speed difference whatsoever on my other systems). Oh, and C:MakeDir - appearantly someone thought the creation of directories went too slow at some point.
I can create a section on my website if you wish, with your help, of course. And then we can help Amigaos 3.9 on 68000 move forward. This would be particularly interesting for both the Minimig and the soon to be released fpgaarcade (which IMHO makes it even more interesting).
I can upload a list of files, versions and md5sums for example. I will update my kick39.rom with BB4 stuff as well (if possible), and can give you that as well. I don't see much future for it though, since all bug fixes and feature additions only happens (mostly silently) with 020+ in mind. FPGAArcade will hopefull have the option of having a CPU board with a real 68k on it, as freely available 020+ softcores have yet to appear. My A500 will have a 020 quite soon, and making it even less of an issue for me.