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

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.

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)

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.

Logged

"There is a concept which corrupts and upsets all others. I refer not to Evil, whose limited realm is that of ethics; I refer to the infinite."Jorge Luis Borges, Avatars of the Tortoise. --Jumalauta!!

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.

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.

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.

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.