Hi... what is one supposed to do with prepared package? I took a liberty of simply trying to upload it to beta/ and incoming/ directories on nekochan ftp, but was out of luck in both cases. Is there some magic login/passwd combination that I missed, or some more formal process that I should adhere to?
The collected works of ant_39
I must have mistyped the path yesterday, I've just tried it now (with console ftp, just as yesterday) and the file (neko_expect-5.44.1.tardist) was accepted in incoming.
pub_bronx wrote: Hello,
I've just uploaded links2 .
My first published tardist... Hoping that everything will be ok.
PB
Yay, links! I love this browser, actually used it for quite a while exclusively. It's good to have it or irix!
As for the packaging, I miss spec and idb files. They usually come in "distribution files" folder I think. Being quite new in packaging, I'll welcome corrections, but this seems to be implied by Packaging_Software wiki page.
Guys,
I just uploaded neko_Squeak-3.9.8.tardist to incoming. Squeak is an implementation of the powerful Smalltalk programming language and environment.
Enjoy.
Benchmarks on 500MHz Fuel:
Compared to the results reported on Squeak site, this rather sucks; and this is already built with -OPT:Olimit_opt=on, which tripled the performance. I suspect this is due to quick'n'dirty way I "fixed" their use of inlining, viz. #define inline to empty string. In near future, I may look into this issue, and find the proper way to do inlining in mipspro.
I just uploaded neko_Squeak-3.9.8.tardist to incoming. Squeak is an implementation of the powerful Smalltalk programming language and environment.
Enjoy.
Code:
MD5 (neko_Squeak-3.9.8.tardist) = 8fec41aaf26dde2134da25845b7b8ca1
Benchmarks on 500MHz Fuel:
Code:
5 tinyBenchmarks
'18068887 bytecodes/sec; 904535 sends/sec'
'18068887 bytecodes/sec; 904535 sends/sec'
Compared to the results reported on Squeak site, this rather sucks; and this is already built with -OPT:Olimit_opt=on, which tripled the performance. I suspect this is due to quick'n'dirty way I "fixed" their use of inlining, viz. #define inline to empty string. In near future, I may look into this issue, and find the proper way to do inlining in mipspro.
ant_39 wrote:
I just uploaded neko_Squeak-3.9.8.tardist to incoming.
Uploaded version with fixed up dependencies, namely removed dependency on expect. This is such a small change that I didn't even bump a package version.
I just uploaded neko_mpfr-2.2.1.tardist to incoming. The MPFR library is a C library for multiple-precision floating-point computations with correct rounding. MPFR is based on the GMP multiple-precision library (which already is packaged for nekoware).
Testsuite passes, but I had to degrade the optimization to -O2. No patches were necessary.
Enjoy.
Code:
MD5 (neko_mpfr-2.2.1.tardist) = ce3fc6d3b81603e3cc1f693acff546ae
Testsuite passes, but I had to degrade the optimization to -O2. No patches were necessary.
Enjoy.
joerg wrote:
LOL, i build the same software for nekoware a few hours ago because a friend of mine need it for building gcc 4.x.
Heh, same here, but the person building gcc was me :) Last time I built mpfr locally just for gcc, but I did whole-tree rebuild now, and thought heck, why not do a proper package :)
joerg wrote:
There is a odd thing about "/usr/nekoware-build/share/info/dir" which contains only a description of npfr. But the filename isnt very specific and i think "gmake install" makes something wrong. So its good that your package doesnt contain this file.
This file is a common byproduct of installing info pages. "dir" is a directory with references to all the info pages installed on a system. When it doesn't exist, installation procedure creates a new one.
On my installation, info files are in /usr/nekoware/info; in /usr/nekoware/share/info there is currently only mpfr page. Possibly the installation process is hosed in how it handles info pages.
joerg wrote:
Btw. I prefer to assing files from nekoware/share to the sw.eoe subimage because most time it contains stuff which is need for running the binary. Thats not true for npfr but i think "man.manpages" isnt the right place for it.
Well, it's a documentation that serves the purpose very similar to man page. It's in no way necessary for mpfr runtime. I think "man.manpages" suits them well.
Thinking about it, packaging the info file without post-install command "install-info" is wrong, too, because then the info page isn't in "dir". I will fix that, but will first have to experiment with pre/post-install commands a bit, e.g. how it handles package upgrades.
Therion wrote:
I just added
neko_windowmaker-0.92.0
;)
Ooh... gotta check that! WM is my favourite!