[Raion]

Finally getting around to touching some of my work with rebuilding this in the past, I decided to take this approach again for various reasons. 

The core packages that I have identified as being useful to most people in the 21st century are about 352 from the current repository. We will probably have 4-5 additional for infrastructure purposes, including new GCC releases. My plan for Nekoware is still to maintain MIPSPro basis on various packages, only using GCC versions 4.9.5 and 8.2 as needed. These versions were picked for various reasons, but the main one is for simplicity and being "easy" to compile. Because of various reasons my idea of a GCC SDK did not prove as simplistic or well thought out primarily because of the use of libgcc.so in the need for multiple bootstraps resulting in a situation where you have a lot of interdependent libraries. That doesn't mean that such a thing won't come to fruition one day but I am hesitant but a new release of nekoware should include such a thing. 

Any new release is going to take a while. Don't know how long until I start digging into it again but one of the major things is going to be jumping versions and documenting/fixing various dependences. 

The new version will still use gettext and GNU iconv in an attempt to be drop in, but some of the main differences are is that I won't be rebuilding any GNOME, KDE, webserver or other ancillary packages. This is both done to optimize things, as I anticipate at first I will be the primary maintainer and tester of a lot of this, and to simplify things.

[jirka]

Wow, Thanks for update!

I still use the "old" nekoware on my "main" SGI, the O2. I feel that some updates would be very nice!

[Raion]

My goal will be to make maintenance of the old NW as easy as possible, so anyone can "adopt" a package.

[Trippynet]

Good work! Maybe this might motivate me to fire up one of my systems at last. They haven't been run for some time, I kind of lost some motivation after numerous PSU issues with my Indigo2, but my Fuel should still be functional, as should the O2 in my cupboard.

[markh]

I have created a tardist of bash (5.1.16). Is there somewhere I can upload it so someone can test it? As it is my first tardist, I am sure there are things that are wrong/can be improved.
I have installed it on my own machine and the basics seem to work fine, but I only needed it to get some other package compiling so I haven't done much with it. I normally use tcsh.

[Raion]

Catbox.moe -- I'll test it and if it's good enough for us I'll put it in the next round of Nekoware. Can you screenshot the subsystem topology for it?

[markh]

I have uploaded it there and the url is https://files.catbox.moe/kopnzm.tardist

I am not sure what you mean by the topology, but I uploaded a screenshot of the swpkg screen: https://files.catbox.moe/efntpi.png
Let me know if that is not what you wanted.

[Raion]

You did it right sir. I am downloading it now, and I'll create a new nekoware packagesite. If you want to maintain yourself as a maintainer for packages like this, lmk what packages interest you.

[markh]

My goal is to get git working and make a tardist of it and all dependencies it needs.
I managed to get git working, but I still need to compile "less" as I can see it being called from git for some functions so that is my next target. Also, the git install seems to be missing at least the man pages, so I need to look into that.

I created a github repository to help me build and package the software. It is at https://github.com/markhellegers/nekoports
I copied the idea from Haikuports (https://github.com/haikuports/haikuports) and wrote a Perl script to build and package the software (works with the version of Perl shipped with Irix 6.5.22).
So far, I only have one package (bash), but I intend to add more. I will then also need to expand the Perl script as I only added enough to the script to get bash to work.

[Raion]

I don't have a GitHub account but I will gladly assist you if you have any questions or problems.