Well, I tried really simple thing today: to compile some C SW . It is something what I did countless times in Linux. In Windows, I wrote some utility SW in C. All it went without any bigger hassle, actually smooth.
But, we have some real geniuses in our Atari community, who will make trivial task to be real headache.
And it was after claimed hard work to put it all together, doing some necessary corrections in source files and tools.
"COMMAND.TOS should work" - no it works not. How much time it takes to try it self to be sure is work or not ? Less than minute, really. And there are other similar examples. After looking some threads, I think that I know how to solve it - not surprise, must using exactly everything same as person who made that package. What will need some time to find and DL, install that SW . Not today ...
Not surprise that it is man in team, which works on another shouldworkware SW project. - will not name it. Just will describe how it works in reality. Some will guess it immediately, I'm sure. That SW is champion in incompatibility - about 65% of SW I tested fails with it. But hey did everything by docs. If something works not, blame that SW. Nope. they could not do everything by docs. Simply because no complete documentation. And even if they would exist, only real criteria is test. But they don't like to test. It's easier to say: should work.