Ok slightly confused, (hope I'm not wasting your time with this Jim)
I just checked that url you provided. There is no mention of the
"install" command, which I found by running buildout --help. Here's
the text:
Commands:
install [parts]
Install parts. If no command arguments are given, then the parts
definition from the configuration file is used. Otherwise, the
arguments specify the parts to be installed.
Interestingly (i.e. what confuses me)
If I run
$ buildout buildout:parts = part1
Part 1 is built and all of part1's dependencies.
However if I run
$ buildout install part1
Part 1 starts to build but in my case bombs because part 1's
dependencies aren't built.
So as a new buildout user I'm confused about:
1. The purpose of the install command
2. Why it doesn't build dependencies.
On 3/12/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
>
> On Mar 12, 2007, at 12:40 PM, Scott Robertson wrote:
>
> > Thanks Jim,
> > I stumbled upon that myself this weekend wasn't sure if it was
> > appropriate.
> >
> > One thing I noticed, is that if you use the "install" keyword on the
> > command line i.e.
> > $ buildout install some-section
> >
> > Dependent sections don't get built (is that intentional?)
>
> Yes, and documented (http://www.python.org/pypi/zc.buildout#command-
> line-usage).
>
> If you want to install a part and its dependents, use:
> buildout:installed=partname,
> or, for multiple parts: "buildout:installed=p1 p2 p3".
>
> Jim
>
> --
> Jim Fulton mailto:[EMAIL PROTECTED] Python
> Powered!
> CTO (540) 361-1714
> http://www.python.org
> Zope Corporation http://www.zope.com http://www.zope.org
>
>
>
>
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
