Some of the Enthought packages are already in yum repositories. However, they all are not named so you can easily see that they are indeed Enthought packages. So if you want to install a collection of packages, you have to go through the list of packages (such as using "yum info python*") and notice the names.

Also, over the past few years I have built rpms for the Enthought toolset. However, the last few times I ran into problems. I recently tried to download the latest tagged version recently from the Enthought svn repository and ran into the problem that the version I requested was not recognized. The previous time I tried I ran into the "unpackaged files" problem, because there was some kind of glitch in rpm.

I did take the tool for building eggs of all their packages and modified it into a tool for fixing the setup.cfg files. Another problem I ran into in the past was files and directories named appropriately for Windows but not for Linux, i.e., with spaces in the file/directory names. I worked most of them out with the people at Enthought, but I later found that it is a problem that still needs watching. There are several other glitches that you run into trying to build the rpm packages.

As I said in a previous posting, it would also be nice if bdist_rpm made use of the same rpmbuild directory tree as other rpm builds and did not build the rpms within the svn repository (or at least provided an option to do so).

Stan Klein

On Fri, March 19, 2010 8:00 am, Toshio Kuratomi a.badger@gmail.com and Gael Varoquaux gael.varoquaux@normalesup.org wrote:

Message: 3 Date: Thu, 18 Mar 2010 15:17:23 -0400 From: Toshio Kuratomi a.badger@gmail.com Subject: Re: Python SIG To: Fedora Python SIG python-devel@lists.fedoraproject.org

On Thu, Mar 18, 2010 at 03:11:15PM +0000, Jos? Matos wrote:

...

On Wednesday 17 March 2010 19:36:35 David Malcolm wrote:

...

How about this: "A SIG for people who are interested in Python on Fedora. This

includes

...

packaging and optimizing the various Python 2 and Python 3 runtimes (CPython, Jython), packaging libraries and applications, setting and improving standards for packaging them as RPM's and maintaining Python packages for Fedora." (somewhat copied from Ruby)

I find this a good start (just as you do). :-)

Just to add to the discussion my main interest in this SIG is on scientific and/or educational python packages.

What we see, in terms of packaging, in projects like sage http://www.sagemath.org/ or in other projects (proprietary) like EPD (Enthought Python distribution) or Python(x,y) is that put everything under the sun on those packages.

It would be nice to have the free parts in Fedora...

Such as the above statement is written I see these goals there.

WRT enthought, they're very interested in getting their software packaged for individual distributions but don't have any manpower or inhouse knowledge on how to do that. If someone were to start working on those packages, I could pass along contact information and we could potentially have help from them on changing their packaging over time to address our needs.

-Toshio

---

Message: 4 Date: Thu, 18 Mar 2010 20:23:32 +0100 From: Gael Varoquaux gael.varoquaux@normalesup.org Subject: Re: Python SIG To: Fedora Python SIG python-devel@lists.fedoraproject.org Message-ID: 20100318192332.GB16916@phare.normalesup.org Content-Type: text/plain; charset=iso-8859-1

On Thu, Mar 18, 2010 at 03:17:23PM -0400, Toshio Kuratomi wrote:

...

...

Such as the above statement is written I see these goals there.

...

WRT enthought, they're very interested in getting their software packaged for individual distributions but don't have any manpower or inhouse knowledge on how to do that. If someone were to start working on those packages, I could pass along contact information and we could potentially have help from them on changing their packaging over time to address our needs.

AFAIK, that's been partly done (mayavi2 is packaged under Fedora, I believe).

I believe that Rakesh Pandit is the one to thank for that work.

I second that assersion though: Enthought is interested in protecting and selling only the binaries of EPD. Enthought would like the corresponding software (all open source) to have as much success as possible, and thus to have high-quality packages on every platform.

Disclaimer: I worked for Enthought (although only a very brief amount of time, as I am pursuing a career in academia), and I have much personal interests in the success of the various Enthought-related packages, but little time for packaging work.

Ga?l