090219 numpy-1.2.1 [VL 6.0]

[caitlyn]

Blurymind has packaged numpy for VL 6.0.

Package:  numpy-1.2.1-i586-1vl60.tlz
MD5:  4a51b7bc80bcafaf629b1d7678a329d8
Package Size:  1470K
Installed Size:  7610K

Sources:  http://vectorlinux.osuosl.org/veclinux-6.0/source/testing/dev/numpy

Code:

numpy: The package needed for scientific computing with Python
numpy:
numpy: Numerical Python adds a fast and sophisticated array
numpy: facility to the Python language.
numpy:
numpy:
numpy: License: OSI-Approved Open Source
numpy: Authors: see website
numpy: Website: http://numpy.scipy.org/

After testing this package please stop back here and let us know how it works for you.

[Windozer]

Thank You BlurryMind and Caitlyn!

- H

[blurymind]

 

my original intent for this package is to get mypaint to work...But thats not going to happen soon.Not until pygtk is recompiled with numpy support.

[Windozer]

Yes, noted that in another thread... but I'm still glad you did this, as I've been using numpy on windows and a debian distro... it's nice to have it available on VL. I'm going to run it through its paces tomorrow and will post results...
thanks again,
- H

[Windozer]

Sweet!
"""
Running unit tests for numpy 1.2.1
Python version 2.5.2
nose version 0.10.4

Ran 1740 tests in 1.177s

OK (KNOWNFAIL=1)
<nose.result.TextTestResult run=1740 errors=0 failures=0>
"""

[blurymind]

windozer, Thank you for testing and using it.It really makes me feel that I've done something useful. 

[Windozer]

You bet, and thanks again for setting it up.

A lot of the python stuff can just be downloaded and installed directly, of course, but the packages make it so much more mindless ... because you have done the thinking up front for the rest of us!  Looking forward to pygtk too. 

- H

[blurymind]

well,if nobody else repackages it with numpy support,i will have to do it by myself..or i'll never be able to use mypaint on vector linux,which will be a real shame. There is not much painting software for linux.I'd say that mypaint is the only single native one that works =( (krita is still quite useless)

[rbistolfi]

Blury, I was planning to do that but I am very busy atm, for this kind of packages, I would say that is safe to get the current slackbuild and add what you need. What I do is test them as much as I can, and ask some other packagers to test it also.

If you can wait a few days I can give it a try.

[blurymind]

Blury, I was planning to do that but I am very busy atm, for this kind of packages, I would say that is safe to get the current slackbuild and add what you need. What I do is test them as much as I can, and ask some other packagers to test it also.

If you can wait a few days I can give it a try.

This is something i was meaning to ask..Where is VL's official slackbuild repository? Does it have to do with vpackager?
I want to repackage it using a safe slackbuild.

[caitlyn]

Each version of VL has a source repository.  For VL 6.0 it's at:  http://vectorlinux.osuosl.org/veclinux-6.0/source/
For VL 5.9 it's at: http://vectorlinux.osuosl.org/veclinux-5.9/source/  The structure of the source directory parallels the binary (package) directory, meaning it has the same categories.  Once you're in a category (i.e.: dev) there are folders rather than package files.  In each folder there is another folder for each version of a given piece of software that's been built.  Inside that are the slack-required, the slack-desc, and and a src directory.  The original source code, any patches needed, the SlackBuild, and anything the package builder created specifically for the package (icons, a .desktop file, etc...) are all in the src directory.

For example, let's take rbistolfi's bpython package.  It's not on the iso so you'll find it in extra/dev.  The SlackBuild resides in:  http://vectorlinux.osuosl.org/veclinux-6.0/source/extra/dev/bpython/0.7.1/src/

It is perfectly acceptable to recycle a VL 5.9 SlackBuild so long as it meets current standards.  Just change the version number to the one you're actually building, the packager name, and the build number accordingly.  In general, unless a piece of software hasn't been updated since the VL 5.9 package was built, you'll want to grab the latest and greatest stable source code and build that rather than recycling the source in the VL 5.9 repo.

HTH,
Cait

[Windozer]

Caitlyn,

that was helpful - might be good to put a similar, but timeless, readme at the top of the source directory.  I mucked around in there for a long hour before understanding the layout.

Rodrigo,

thanks for doing all the Python stuff ... couldn't help but notice IPython in ./dev    And I'm trying out bpython now --- that one is new to me --- looks promising!

- H

[Triarius Fidelis]

Thanks blurymind

[blurymind]

Cait...I can't seem to find a pygtk slackbuild/directory at the repo.. 

[caitlyn]

Neither can I.  Its a converted Slackware 12.1 package if that helps.

Please take this up with the core developers.  There are still packages on the VL 6 iso that aren't in the repo at all or lack sources.  This is a GPL violation so it is serious.   However, I have no control and very little influence over what the core developers do.  I personally find this particular situation very frustrating.  I've raised the issue before to no avail.