Pakaging enthought tool suite

[Ignacio Vazquez-Abrams]

On Thu, 2008-04-10 at 17:52 +0200, Gael Varoquaux wrote:
> 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?
> 
> We are using setuptools to declare dependencies. I don't see an obious
> way of generating a dependency graph from setuptools. We also have all
> the interproject dependencies listed in
> https://svn.enthought.com/enthought/browser/project_map.ini, using a
> home-made dependency-inspection tool.
> 
> I am having a look at seeing how this tool can be used to generate such
> graph. I will post the result on the list (don't hold your breath, I am
> also working on some day work).

Well, we don't need a graph per se; I think that file should be enough,
thanks.

-- 
Ignacio Vazquez-Abrams <ivazqueznet at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-python-devel-list/attachments/20080410/9c4d1963/attachment.sig>