[mgtremaine]

I've started a cleanup project on my (our) last SGI (Hostname: Saiph  Type: o2). I perhaps foolishing installed all of Nekoware back in 2008 or so and now I want to remove unneeded software, update software that can and should be updated. So I'm going keep some notes/observations here and ask for help when I hit tricky bits...

Today I removed (using Software Manager). I'm edit this lit as I move through it all.

Removed (No Issues):

Evolution 2.4
Gaim (and neko_guification)
dovecot 1.0.2
bash 3.1
autoconf 2.60
automake 1.11.1
apache 1.3.37
tiff 3.8.2  ->>>> Breaks Xfe, Evince, GIMP tiff support, Povray even with tiff 4.0.3 installed.
stella 1.4.2
window maker (and -extra)
e16 Enlightenment
Bochs
JBoss
BitchX

Removed With dependents

Php 5.2 removal forces nessus removal  and pdflib  (as well oggvorbis wrapper). I can live with out Nessus it would be so out of date and I have OpenVas on more then 1 other server)
tiff 3.8.2  ->>>> Breaks Xfe, Evince, GIMP (tiff support), Povray even with tiff 4.0.3 installed.  neko_tiff in obsolete is 3.8 so I will restore it.

Oddities:

Package: "My Product" as it appears in SWMG is actually "Paraview" from the Nekoware package. Anyone know anything about paraview? It's looks interesting ut it's a shame the Package naming is just flat out wrong.



Upgrade Goals:  (My List of Nekoware that I really want newer versions of installed via what clean method possible)

Python 2.4 -> 2.7 last
Perl 5.8 -> 5.12+ would be nice
Python 3.1 -> 3.4+ (32bit limit?)
openssl 0.9.8 -> something useable in the 1. series
bash 4.2 -> Bash 4.4 or 5.0


.
.
.

-Mike

[dexter1]

Have a look at my dual mips3/mips4 nekoware distribution, see link below.

Perl 5.24.0 is available, as is openssl 1.0.2
I'm currently working on python 2.7.16 (with 2.7.18 coming out in march). That should be out in february.
Python > 3.1 is tricky since much of the IRIX compiler support and os-specific modules have been removed.

Please note that my packages are a clean rebuild and have, outside of my package directory, no other dependencies than vanilla IRIX 6.5.22m. This is to make sure both mips3 and mips4 versions work fine, which makes nekoware now usable from Indigo1 machines up to Tezro's and Origin3800's.
The downside is that installing from my directory will replace older nekoware packages and will break library dependencies in the packages you have already installed. Please consider this a warning :-)

[TruHobbyist]

Oddities:

Package: "My Product" as it appears in SWMG is actually "Paraview" from the Nekoware package. Anyone know anything about paraview? It's looks interesting ut it's a shame the Package naming is just flat out wrong.

This happens when you forget to "copy over/apply" the changes using the arrow button in swpkg. 

[Raion]

If you guys want a Nekoware repository at the centre I'm willing to help, but we will probably need contributions to help with this. I do not have the ability with the current infrastructure to host an FTP/RSYNC mirror securely for nekoware and I cannot afford to upgrade our infrastructure further.

[mgtremaine]

Paraview looked interesting but on 200mhz 1GB o2 not sure I'm going to use it, so I removed.

I'll check out the upgrades dexter, ty...

The Dependencies on Python 2.4.1 from nekoware and extensive. Screenshot.

   

-Mike

[dexter1]

If you guys want a Nekoware repository at the centre I'm willing to help, but we will probably need contributions to help with this. I do not have the ability with the current infrastructure to host an FTP/RSYNC mirror securely for nekoware and I cannot afford to upgrade our infrastructure further.

My current spin on Nekoware is a large departure from the old standard, because of me including mips3 support. Also, i kinda realize that i am the only one currently doing Nekoware packages after Nekochan went down. And because i want to retain some quality in the packages i'm making (and not creating packages with "My Product" as a package name :-) ) i for now decided that my home webpage is fine, so i'm good. I don't need the nekodeps script and rsync/ftp stuff running on my content, unless there is substantial demand, but i kinda doubt that.

If people want a quality rendition of Nekoware, my pick would be the Rainer Canavan stuff in Nekoware/beta/canavan and i believe we already have that included in the nekoware mirror

[dexter1]

The Dependencies on Python 2.4.1 from nekoware and extensive. Screenshot.

Scary, right? This is why it is essential to have a proper python first, before you can build the packages that rely on python.
Also, Python modules have many dependencies on other lower level libraries so before you can build Python, you need to do those first, which is why it took me two years to arrive at this point.

[mgtremaine]

For sure.. I noticed I have Python 2.7.1 installed also but it doesn't have any visible conflicts. I'll take my time unwinding all this. First pass to remove things that are so outdated as to be useless or that simply can not be run on this low end SGI and/or really not needed.

Then I'll tackle the Python, Perl, Openssl madness that awaits. (I mirrored off your repo and dumped into my NFS thanks again)

So far the only stumble was the TIFF-3.8.2 removal that broke XFE. (Conflict not listed of course)

-Mike

[mgtremaine]

Note about TIFF 3.8

As pointed out above the removal of TIFF 3.8 support silently breaks a lot of things. My incomplete list of Nekoware software that I found to be linked against it is

XFE
Evince
GIMP
Povray
Audacity

I couldn't figure out ho to restore neko_tiff from obsolete without breaking the current one so I downloaded TIFF 3.9 and compile with gcc 3 and installed it into /usr/local at that point the broken software worked again for me.

#### Simple as ...
wget http://download.osgeo.org/libtiff/tiff-3.9.7.tar.gz
gunzip tiff-3.9.7.tar.gz
tar -xf tiff-3.9.7.tar
cd tiff-3.9.7
export CC=gcc
./configure --prefix=/usr/local
make

-Mike

[mgtremaine]

I hear you hamei! I've thought several times I should just start over. But oh well, I've made it pretty far, lots of server stuff I didn't need either (BIND IMAPs etc). The hard part of the un/install is coming with trying to deal with the openssl /python etc..... If I break it all that point I might go for the fresh install.

-Mike