Backporting to NEXTSTEP 3.3

[eiked]

Some of yours might remember NeXTSTEP 3

Compiling any recent software on NS3 is quite hard. NS3.3 was Reno, but not yet BSD4.4, pre Posix.

NS3.3 came with the orginal BSD bourne shell and the original m4, with gcc 2.29, etc which makes just makes every modern ./configure fail.

I got some way up, getting me some oldish bash first, and working up my way, the versions of all the tools.

I did stop at posix threads, while I'm pretty much sure that this can be implemented in terms of Mach cthreads. We should copy this from Darwin.

--- I excuse: backporting to NS3 is only of limited interest.

Please give me some advice: Should I base this on macports? Should I go pkgng?

Homebrew is not an option, because homebrew needs a recent ruby. I want to play ruby on my cube.

That's what it is all about. getting the software up step by step, from the heritage of NS3/BSD4.3/Mach2.5 up to compile all of the new kit. (without any changes to the kernel interface -- all is user space!)

[ryandesign (Ryan Carsten Schmidt)]

I don't think we are interested in changes to MacPorts base to enable it to run on NeXTSTEP. Even if MacPorts base itself could be modified to do so, NeXTSTEP 3.3 was released 20 years ago and I doubt many of our ports could be compiled on a system that old. We currently run on OS X 10.4 Tiger and later, which is already rather pushing it in terms of compatibility with old systems, Tiger having been released over ten years ago; a great many ports already fail to compile there.