Christophe Combelles a écrit :
Hi,
It seems that the 'versions' information in a buildout has a priority
over 'develop'?
What I wanted is to use the exact versions of the KGS:
extends = http://download.zope.org/zope3.4/versions.cfg
versions = versions
Then for a particular egg (say,
On Feb 22, 2008, at 7:23 PM, Christophe Combelles wrote:
Hi,
It seems that the 'versions' information in a buildout has a
priority over 'develop'?
Yup
What I wanted is to use the exact versions of the KGS:
extends = http://download.zope.org/zope3.4/versions.cfg
versions = versions
Then
Hi Jim
Betreff: Re: [Zope-dev] buildout 'versions' and 'develop' conflict
On Feb 22, 2008, at 7:23 PM, Christophe Combelles wrote:
Hi,
It seems that the 'versions' information in a buildout has
a priority
over 'develop'?
Yup
What I wanted is to use the exact versions
Jim Fulton a écrit :
On Feb 22, 2008, at 7:23 PM, Christophe Combelles wrote:
Hi,
It seems that the 'versions' information in a buildout has a priority
over 'develop'?
Yup
What I wanted is to use the exact versions of the KGS:
extends = http://download.zope.org/zope3.4/versions.cfg
On Feb 23, 2008, at 9:14 AM, Roger Ineichen wrote:
...
What do you mean by:
develop eggs are also used for many system package installs :(
See: http://peak.telecommunity.com/DevCenter/setuptools#install-command
This is the technique that Ubuntu uses to install eggs into the Ubuntu
system
On Feb 23, 2008, at 9:26 AM, Christophe Combelles wrote:
I don't have enough experience with all the use cases of buildout
and the develop-eggs, but at a first glance, I find it more logical
to give priority to 'develop':
'develop' is supposed to point to a real path containing a setup.py,
Hi. I agree with Jim. Buildout is doing the right thing. This is not a
conflict since you have explicitly identified the software with a
version already. I think the right thing to do under the circumstances
would be to append a custom versions.cfg to nail the versions you want.
KGS versions
David Pratt a écrit :
Hi. I agree with Jim. Buildout is doing the right thing. This is not a
conflict since you have explicitly identified the software with a
version already. I think the right thing to do under the circumstances
would be to append a custom versions.cfg to nail the versions
Previously Christophe Combelles wrote:
David Pratt a écrit :
Hi. I agree with Jim. Buildout is doing the right thing. This is not a
conflict since you have explicitly identified the software with a
version already. I think the right thing to do under the circumstances
would be to append a
Hi Christophe. Wichert has just responded with the point I was going to
make in reply. I can agree with your point that emitting warnings are
helpful for misconfiguration or if there has been duplication. I am
opposed to incorporating the type of automatic character that has been
suggested.
Hi all
Betreff: Re: [Zope-dev] buildout 'versions' and 'develop' conflict
[...]
I don't think this is a matter of implicit versus explicit,
because there are two explicit configurations: one explicit
'version', and one explicit 'develop'.
I think the question is about what to choose
On Sat, Feb 23, 2008 at 05:22:29PM +0100, Christophe Combelles wrote:
I don't think this is a matter of implicit versus explicit, because there
are two explicit configurations: one explicit 'version', and one explicit
'develop'.
I think the question is about what to choose between two
On Feb 23, 2008, at 11:22 AM, Christophe Combelles wrote:
I don't think this is a matter of implicit versus explicit, because
there are two explicit configurations: one explicit 'version', and
one explicit 'develop'.
The develop option just causes a develop egg to be created. It
doesn't
On Saturday 23 February 2008, Jim Fulton wrote:
Despite my response to him, I'm not entirely sure. I'm curious what
other people think,
For me this is more a question of whether I can override version definitions.
If the following is possible, I like the current method:
[buildout]
develop
On Feb 23, 2008, at 3:06 PM, Stephan Richter wrote:
On Saturday 23 February 2008, Jim Fulton wrote:
Despite my response to him, I'm not entirely sure. I'm curious what
other people think,
For me this is more a question of whether I can override version
definitions.
If the following is
On Saturday 23 February 2008, Jim Fulton wrote:
The additional version specification should be merged into the
extends version
section. The version 1.3.1dev is the version the develop egg
specifies.
Yes. That's how it works now.
Cool, then I think the behavior is correct. I think it
Stephan Richter schrieb:
On Saturday 23 February 2008, Jim Fulton wrote:
The additional version specification should be merged into the
extends version
section. The version 1.3.1dev is the version the develop egg
specifies.
Yes. That's how it works now.
Cool, then I think the behavior
Hi,
It seems that the 'versions' information in a buildout has a priority over
'develop'?
What I wanted is to use the exact versions of the KGS:
extends = http://download.zope.org/zope3.4/versions.cfg
versions = versions
Then for a particular egg (say, z3c.menu), use a develop-egg instead:
18 matches
Mail list logo
