The Enthought Tool Suite (ETS) is a collection of components developed by Enthought to construct custom scientific applications. It includes a wide variety of components, including:

• an extensible application framework
• application building blocks
• 2-D and 3-D graphics libraries
• scientific and math libraries
• developer tools
• MayaVi Data Visualizer

It is available for Linux, Mac OS X and Windows, but they don't provide binaries for OpenSUSE, I don't now why.

Here are just some steps to get it running on OpenSUSE 10.3. But, you have to install some packages, check here before to proceed:
My system:

ionut@vaio:~> cat /etc/SuSE-release
openSUSE 10.3 (X86-64)
VERSION = 10.3

I installed the suite in /usr/local/lib64/python2.5/site-packages so, let's create the directories:

sudo mkdir -p /usr/local/lib64/python2.5/site-packages

Get the souces for ets tool from their repository:

svn co https://svn.enthought.com/svn/enthought/ETSProjectTools/trunk ETSProjectTools

Build ets (it is a kind of wrapper for their repository), a tool that automates the checkout process.

cd ETSProjectTools
python setup.py install

Get the latest souces for the project files, and build the eggs for the components:

ets co ETS
cd ETS_3.0.0b1
svn export https://svn.enthought.com/svn/enthought/sandbox/egg_builder.py
python egg_builder.py

If the build was successful, you would not have received any errors (though there will be one warning at the end about not building egg.info files) and the built eggs would be residing in a directory called dist

Install the eggs in the directory which we created at the beginning:

sudo easy_install -f dist/ -H dist/ ETS

Now you can try some examples which are included:

• check if Traits is working:

python Traits_3.0.0b1/examples/demo/Applications/converter.py

• check if Mayavi is working:

python Mayavi_3.0.0a1/examples/mayavi/scatter_plot.py
python Mayavi_3.0.0a1/examples/mayavi/streamline.py

or just run mayavi2 command.

In my case everything is working fine, I hope that also for you. Here are some references:

• Installation on Ubuntu_7.10_i686
• Installation on Fedora_8_i686
• Source code
  

After announced on March 11, 2008, official openSUSE forums has been established and starting work for providing better support for openSUSE community on June 09, 2008. Forums merges 3 existing openSUSE forums, suseforums.net, suselinuxsupport.de and the openSUSE support forums at forums.novell.com.

You could use single sign-on login with your Novell/openSUSE account. It’s also should be work with your existing account at existing forums but I didn’t try it ;-), so, please try to login before create another new account.

Thanks for all of Novell staff and openSUSE community members who make the dream come true. Quoting what Michael said last 3 month : “a big gain for the whole openSUSE Community !”

It would be nice if libzypp had some framework that allowed to implement extensions like e.g. a history of installed and  removed packages easily.

I’m currently looking into the boost signals library to see if we could use it to provide hooks for such extensions.

A  future  ZYpp::commit would then emit signals e.g. before and after installation/deletion of packages. Some extension code could then connect to those signals to create e.g. such a history.

Another candidate would be the repository management emitting signals as repositories are added removed refreshed.

Last week, me and 2 Indonesian openSUSE members : Bonnie Kurniawan & M Herry Nurdin holds a training session at Grha Pemuda & Olah Raga (Youth Fellow & Sports Building), State Ministry for Youth Affairs and Sports of the Republic of Indonesia, Senayan, Jakarta.

Training focused on openSUSE server function and administration, with an overview about openSUSE 11.0 features and capability. There are totals 20 audiences on first and second day, and 40 audiences on third day, came from sub dept of State Ministry for Youth Affairs and Sports and they will administer openSUSE server on their office. Most of the audiences are newbie for Linux but they have no problem with openSUSE administration. They looks a quite bit worried when we got an introduction about Command Line Interface, but after a few minutes, they’re enjoy the training.

Training taking full 3 days to complete, started on June 07 2008 until June 09, 2008. I gave a presentation and practical guide for openSUSE installation (hey, it’s pretty nice to show off openSUSE installation process. It needs a few step only, with yes, no and next ), domain controller and active directory with samba, Apache Web Server and Virtual Host and an introduction about YAST usability.

I have a small discussion about Indonesian openSUSE community with Edy Purwanto, IT administrator for State Ministry for Youth Affairs and Sports office, and he promised to helped us setting up and provide openSUSE mirror by using dedicated server and dedicated internet access in his office. Well, it’s a good news for upcoming openSUSE 11.0 release on June 19, 2008. We will set up this server for ISO image and repository download services.

We also distributed openSUSE 11.0 RC1 free CD and DVD plus a set of tutorial for the audiences and told them to contact us if they have any problem with openSUSE implementation at their office units.

If you are doing a lot of Scientific Computing and you want to use Windows as a platform, then my advice is to switch on Linux/Unix. If you don't agree with me then a good solution for you is Python(x,y).

What is it? From their web site:

"Python(x,y) is a free scientific and engineering development software for numerical computations, data analysis and data visualization based on Python programming language, Qt graphical user interfaces (and development framework) and Eclipse integrated development environment."

"Its purpose is to help scientific programmers used to interpreted languages (such as MATLAB or IDL) or compiled languages (C/C++ or Fortran) to switch to Python. C/C++ or Fortran programmers should appreciate to reuse their code "as is" by wrapping it so it can be called directly from Python scripts."

For the complete list of features and its components checkthis page.

For some screenshots check here.

There is some work going on to put installation source creation functionality into kiwi.
At the moment kiwi can use prepared installation sources such as:

• BuildService Repositories
• mounted DVDs
• FTP trees

But what if you have a local Build Service building some binary only packages and you wish tp make a installable media set from, say, “SLES + binary only drivers”?
You can use the inter-BS-Connectivity feature to only build the drivers (and not the whole distribution) in your BS and then create an installation source from your main BS project.

This is possible since release of the package kiwi-instsource which extends the functionality of the config.xmlfile to allow the compilation of an installation source from scratch.
Hereby “scratch” means directories containing .rpm and .spm files. Of course some information must be provided for the metadata creation — but this is also all in the config file (with one known exception — the PDB data).

The rest is figuring out which packages must be on the installation source.
Since it is perfectly ok to have conflicting packages in instsources, there is no dependency check or package resolving in this stage. The information must come from the user.

Therefore the package list may become rather long and I already plan to implement some simplification.
These plans include:

• allowing more than one <repopackages> section
• implement outsourcing blocks in separate files using XML functionality