isn´t layers.library v45 partially based on commodore-sources ?
It most definitely is. Actually, it is a version that is half-way between the 3.1 V40 release and the version in AOS 4.x. The big difference is here, however, that I approached the owner (or at least, the owner "to the best of my knowledge" - what else can you say these days) and asked specifically whether they would be ok with publication. IOW, I tried to back up myself as much as possible to avoid any conflict to begin with.
As for other components, i.e. the Shell, it was part of the contract with H&P what will happen with the copyright after two years, and I'm still trying to ensure that those that can apply these patches have at least the 3.9 version - whether legit or not I cannot verify, of course.
This is pretty much why I said in the beginning - there is probably no problem if Cosmos would just communicate better and would have just *asked*. The worst thing that could possibly happen is a "No". But the current way of acting makes the situation actually worse, not better. It creates a diverse universe of some "almost but not quite" AmigaOs components with slight incompatibilities and no ensured "software contract" that everything fits together as it should.
What I would really prefer would be a somewhat more coordinated activity, as in a project (let it be for paid or unpaid for developers) to create a framework where we can ensure that all components really work well together. That's currently not possible, and it's even less possible with people that cannot simply "play team". I'm trying to ensure that Olaf gets my updates, and that the functions for "layers" are in sync with AOS 4.x such that we don't create branches as far as possible.
Yes, it means making compromises, and it requires a somewhat different development style - and a massively different communication style. If you observe my rather "rough tone" here then that's because I'm personally *p&ss@d" by the amount of unprofessionalism that rather *prevents* than *supports* any coordinated activity. It simply doesn't work like this. It is damaging AmigaOs rather than moving anything foreward.
There isn't much of any type of project management for the "old" classic systems, and it would be so badly needed. It's part of the lack of responsibility of the owners to take these systems serious, most likely based on a return-of-investment reasoning. If the community ever wants to be taken serious, namely that such an investment might possibly worth it, then we should act more professional as a group and not as a collection of freaks (not excluding myself here).