[PEAK] RuleDispatch not on Cheeseshop?

[Phillip J. Eby]

At 09:35 AM 3/3/2006 -0800, Jay Parlar wrote:
>On 3/3/06, Phillip J. Eby <pje at telecommunity.com> wrote:
> > At 04:30 AM 3/4/2006 +1200, Jay Parlar wrote:
> > >On 3/4/06, Ian Bicking <ianb at colorstudy.com> wrote:
> > > > > Hmmm... Maybe I was looking at it wrong, but I was seeing Cheeseshop
> > > > > as Python's own version of the Gentoo Portage tree. I mean, with
> > > > > easy_install, we get all the nice dependency resolution and
> > > > > everything.
> > > >
> > > > Yep, and you still get that.  If you do `Subversion repository
> > > > <http://path/to/Project/trunk#egg=Project-dev>`_ in your project
> > > > description, your package can be installed with easy_install directly
> > > > from that repository.
> > > >
> > >
> > >But that doesn't take the dependency resolution into account, right?
> >
> > Yes, it does.  Whatever is specified in the setup.py in Subversion will
> > determine the dependencies.
> >
> >
>
>Sorry, I must not be making myself clear. Yes, dependency information
>is there in setup.py. The thing is, those dependencies are usually in
>the form of Require("SomePackage"), right? (I know, I probably got the
>syntax wrong).
>
>My whole point, is that packages can go up onto Cheeseshop, and list a
>whole bunch of dependencies. But then those dependencies themselves
>are not available on Cheeseshop (or explicitly listen in the setup
>info), and the install breaks. Is that something that is considered
>"ok"? I would think no.

Right.  But as long as those projects *also* have similar subversion links 
and are listed either under their own names on PyPI, or are linked from the 
same page that pointed to *that* subversion link, everything's 
okay.  EasyInstall can scan any page for links, not just Cheeseshop pages.