On Thu, Dec 11, 2008 at 07:27:58PM +0530, Rakesh Pandit wrote:
On Thu, 10 Apr 2008 23:49:18 +0200, Gael Varoquaux wrote:
>On Thu, Apr 10, 2008 at 01:43:34PM -0800, Jeff Spaleta wrote:
>> > The tarballs of each released packages are located on
> >> You do need a dependency graph to be able to make some
sense of this. I
> >> am making good progress on making a nice one.
>> Just for clarification... the eggs are completely
>> contain binary blobs of any sort?
>Yes. I am not an Enthought employee. I have no financial interest
>other interest than promoting high-quality open-source scientific
I am packaging mayavi2
My current mayavi spec state is:
It does not
build, but I am working on it and would love help or patches. ;)
Great, that's fantastic news. We actually had a release just yesterday
Speaking of which, you are packaging old versions of ETS. The URL for the
new versions are on PyPI (we made the shift to PyPI since this summer,
for the release of ETS 3.0). The standard URL for the tarball for a
package FooBar is:
Debian packages have 'watch' files that check for new versions using a
wildcard for the version number, therefore downloading the tarball is
There are a number of individual projects to package: for the Debian
packages we decided to fit to the exact structure of ETS 3, and we made
12 packages (that includes 3 packages required for chaco, but not
mayavi). Making these packages the first time was some work, and I think
you should try and start from the work we have already done. You can
use alien to convert the debs to rpm. The latest debs can be found at
. You will not need the gastable one:
it has nothing to do with ETS. These packages are not in Debian, because
of Debian freeze, but they are maintained by Varun, the Debian maintainer
of the ETS packages.
The other option would be use the Mandriva RPMs, developped by Lev Givon.
You should use the ones for Mandriva 2009, as these are for ETS 3. I
don't know Mandriva well, so I don't know what would be the best way to
I know that the structure of the debian packages is good, because I have
help making them. I can work with you to extract the relevent information
from them. There is actually very few information that is useful for
packaging, as you want to get only the metainformation: the source
tarball you will grab from the URL described in the package.
I am at work right now and can't spend time on this. I gess that by the
time I get back home, it will be late in India. And same thing tomorrow.
However, during the week end, if you want, we can pop up a chat and get
some work done quickly. I know nothing of RPMs, so I can hardly be useful