Nekochan Net

absolutely -- no offense intended. It's nice to be able to banter with another viewpoint.

i forgot my rose colored glasses today.

cheers.

_________________
The preceding thoughts were brought to you by Jack Daniels.

now im going to have to go read karl marx again and *gasp* ESR's writings for more discourse on the topic.

perhaps i can prove that they are both alien imposters planted here to destroy the human race!

))

_________________
The preceding thoughts were brought to you by Jack Daniels.

ESR? jaysuz i thought "cruel and unusual punishment" was illegal stateside

looks like i started a small war in here
:agrue: :2gunfire: :rightfighter6: :violent1: :violent3: :leftfighter1: :rightfighter5:

Yes my dear fellow earthsmen,

I've said it before

And I'll say it again

...

this site has too many emoticons.

;-D

_________________
Shall I describe it to you? Or do you want me to get you a box?

I'd say so... :withstupid: No insult intended ofcourse... :wickedfart:

:big5: :indian: :rainbowafro:

:smileycouncil:

Yes!, Of course, and I have an agreement with such happy medium of the software developing scheme, but don't forget that the Open Source Community was releasing high quality code. And there are many examples of such sourcecode. Many time better that many commercial applications from many known vendors...

But the main problem to obtain such "happy medium" is the absence of the right tools to protect releases of commercial binarys with their source code on a succesfully licensing scheme. Right now, such field was only used on a form of SDK, or "Software Developer Kits", by a few corporations, and not always they include source code (only headers and objects).

I could be happy to release the complete source code of my programming projects along with the binaries (installers), on a "pay_per_use_only_one_time" basis, so the end user could be not only using the end application: he could "tweak" or "hack" the code, compile, and get new functionalities.

But we like to do such thing on a commodity price basis. And the cost to release a source code to the "big ocean" for a very complex application would be very-very high.

Just consider an app of 12000 man's hours, and you'll be getting an approach...

_________________
Oh!, let me write that!


Octane / Dual Head

http://twitter.com/GeekTronixShop

to me it's two things - first is the matter of quality, where gnu often fails pretty miserably. Second is secret source, which is contradictictory to the purpose of copyright and means that no one can ever fix what the lousy bastards at Adobe or IBM screw up. I don't have enough fingers and toes to count the number of software products I have *bought*, only to have their masters toss them (and me) out in the trash when they got bored. We'll probably never know how much of that was due to Microsoft's enforcers, but still .... I paid, I got screwed. Copyright is fine but the source should go into escrow. When the app is withdrawn from distribution then the source should be freed.




hi cosmos

Back on the track ...

I kindly ask the good guys who compile the packages to at least make also a tar with the modified source and upload-it next to the mips4 binaries ... as my time permits i will get it and try to make some mips3 binaries.

And Neko please, please, please when you link a new software package from the front page don't forget to specify when is mips4 only ...

Thank you very much.

My packages which have started rolling onto this website as of this week are all build for mips4 as clearly stated in the description and dirname, but they all do contain the source code, patches, and build instructions. So no one should have any trouble rebuilding them for mips3 also.
Good luck :-)

_________________
Shall I describe it to you? Or do you want me to get you a box?

Unfortunately I don't always know - I usually don't have time to test these days and not everything comes in labeled as such.

_________________
Twitter: @neko_no_ko
IRIX Release 4.0.5 IP12 Version 06151813 System V
Copyright 1987-1992 Silicon Graphics, Inc.
All Rights Reserved.

Nice way to do it, whiter. Thanks. Also seems like your builds are faster ... maybe wishful thinking tho, I should do some benchmarks.

Now, if we could get everyone to standardize on /usr/neko ....