Pakaging enthought tool suite

Gael Varoquaux gael.varoquaux at normalesup.org
Fri Apr 11 18:31:13 UTC 2008


On Thu, Apr 10, 2008 at 11:32:07AM -0400, Ignacio Vazquez-Abrams wrote:
> On Thu, 2008-04-10 at 16:53 +0200, Gael Varoquaux wrote:
> > I agree that packaging the whole Enthought Tool Suite would be very nice,
> > and much better than shipping it in a coarse-grained set of packages, as
> > Debian and Ubuntu have been doing. Making 15 or so packages is more work
> > than making 4, but it is more value.

> Is there a dependency tree/graph anywhere we can look at to decide which
> pieces to tackle first?

By the way, what can we do, what tools and information can we provide to
make your work easier?

Specificaly, what is your workflow to package a suite of tools with cross
dependencies like the ETS, relying heavily on setuptools? We are having a
internal discussion on how to make it as easy as possible to package ETS
and maintain for downstream, and as none of us has much packaging
experience it would be great to have as much feedback as possible.




More information about the Fedora-python-devel-list mailing list