On Mar 30, 2009, at 1:50 PM, Paul Winkler wrote:
On Mon, Mar 30, 2009 at 12:29:16PM -0400, Jim Fulton wrote:
On Mar 30, 2009, at 12:08 PM, Paul Winkler wrote:
Ian's Pip tool tries to download everything and work out the
complete
graph before doing any installation; I've no idea if any of
On Mar 29, 2009, at 4:10 PM, Wichert Akkerman wrote:
...
You can compare this with dpkg and apt on Debian and Ubuntu systems:
dpkg is the lower level install that installs one or more packages. It
only checks if the packages you install break any package conflicts
and if their dependencies
On 3/30/09 4:04 PM, Jim Fulton wrote:
On Mar 29, 2009, at 4:10 PM, Wichert Akkerman wrote:
...
You can compare this with dpkg and apt on Debian and Ubuntu systems:
dpkg is the lower level install that installs one or more packages. It
only checks if the packages you install break any package
On Sun, Mar 29, 2009 at 11:47:14AM -0400, Jim Fulton wrote:
I think an implementation of a better dependency resolution strategy in
buildout would be a good place to start. I think some limited
backtracking could go a long way. Anyone interested in working on this?
Ian's Pip tool tries to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30.03.2009 11:08 Uhr, Paul Winkler wrote:
On Sun, Mar 29, 2009 at 11:47:14AM -0400, Jim Fulton wrote:
I think an implementation of a better dependency resolution strategy in
buildout would be a good place to start. I think some limited
On Mar 30, 2009, at 12:08 PM, Paul Winkler wrote:
On Sun, Mar 29, 2009 at 11:47:14AM -0400, Jim Fulton wrote:
I think an implementation of a better dependency resolution
strategy in
buildout would be a good place to start. I think some limited
backtracking could go a long way. Anyone
On Mon, Mar 30, 2009 at 12:29:16PM -0400, Jim Fulton wrote:
On Mar 30, 2009, at 12:08 PM, Paul Winkler wrote:
Ian's Pip tool tries to download everything and work out the complete
graph before doing any installation; I've no idea if any of that work
could be ported to buildout, but it might be
Chris Withers wrote at 2009-3-27 16:02 -0500:
...
Got zope.principalregistry 3.7.0.
While:
Installing zopetest.
Error: There is a version conflict.
We already have: zope.component 3.5.1
but zope.app.security 3.7.0 requires 'zope.component=3.6.0'.
Okay, so I thought I'd be smart and try
On Mar 29, 2009, at 3:28 AM, Dieter Maurer wrote:
Chris Withers wrote at 2009-3-27 16:02 -0500:
...
Got zope.principalregistry 3.7.0.
While:
Installing zopetest.
Error: There is a version conflict.
We already have: zope.component 3.5.1
but zope.app.security 3.7.0 requires
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29.03.2009 10:47 Uhr, Jim Fulton wrote:
I think an implementation of a better dependency resolution strategy in
buildout would be a good place to start. I think some limited
backtracking could go a long way. Anyone interested in working on
Andreas Jung wrote:
I think an implementation of a better dependency resolution strategy in
buildout would be a good place to start. I think some limited
backtracking could go a long way. Anyone interested in working on this?
Why would that be a functionality of zc.buildout? I think this
On Mar 29, 2009, at 11:51 AM, Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29.03.2009 10:47 Uhr, Jim Fulton wrote:
I think an implementation of a better dependency resolution
strategy in
buildout would be a good place to start. I think some limited
Tobias Rodäbel wrote:
[zope]
recipe = zc.recipe.egg:scripts
eggs = Zope2
So, this gives you mkzopeinstance, right?
(I don't think you need the :scripts
It worked, as in no errors, but when I tried mkzopeinstance, it
generated an instance, but that instance didn't work:
$ bin/runzope
Jim Fulton wrote at 2009-3-29 12:02 -0400:
...
2. Backtracking is more practical in buildout than with easy_install.
easy_install (not sure about pip) does conflict detection/resolution
at run time, whereas buildout does it at build time. Slow conflict
resolution is a lot more practical
On Mar 29, 2009, at 2:35 PM, Dieter Maurer wrote:
Jim Fulton wrote at 2009-3-29 12:02 -0400:
...
2. Backtracking is more practical in buildout than with easy_install.
easy_install (not sure about pip) does conflict detection/resolution
at run time, whereas buildout does it at build time.
Previously Chris Withers wrote:
If you're proposing fixing it in buildout because getting changes made
to setuptools and then getting a release of setuptools made is damned
near impossible, then that's sad state of affairs for the whole python
community :-(
You can compare this with dpkg
On Saturday 28 March 2009 06:11:30 Chris Withers wrote:
Andreas Jung wrote:
Stop with your approach right now until we have understood what's going
wrong. Working with a SVN checkout from the trunk works (as said).
I'm interested in actually solving what's wrong ;-)
This feels like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.03.2009 15:47 Uhr, Chris Withers wrote:
Hey All,
I'm trying to get Zope 2.12 working with buildout, in the absence of
docs, I thought I'd try:
[buildout]
parts = zopetest
[zopetest]
recipe = zc.recipe.egg
interpreter = py
eggs =
Previously Chris Withers wrote:
Paul Winkler wrote:
Well, yeah. The point of the suggestion was specifically to help you
get more info about the dependency chain, since pip is more verbose
about that than easy_install is.
Well, running buildout -v gives some good clues, a piece of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.03.2009 15:47 Uhr, Chris Withers wrote:
Hey All,
I'm trying to get Zope 2.12 working with buildout, in the absence of
docs, I thought I'd try:
[buildout]
parts = zopetest
[zopetest]
recipe = zc.recipe.egg
interpreter = py
eggs =
Chris Withers wrote:
Got zope.principalregistry 3.7.0.
While:
Installing zopetest.
Error: There is a version conflict.
We already have: zope.component 3.5.1
but zope.app.security 3.7.0 requires 'zope.component=3.6.0'.
Okay, so I thought I'd be smart and try the following buildout.cfg:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.03.2009 16:02 Uhr, Chris Withers wrote:
Chris Withers wrote:
Got zope.principalregistry 3.7.0.
While:
Installing zopetest.
Error: There is a version conflict.
We already have: zope.component 3.5.1
but zope.app.security 3.7.0 requires
Andreas Jung wrote:
Stop with your approach right now until we have understood what's going
wrong. Working with a SVN checkout from the trunk works (as said).
I'm interested in actually solving what's wrong ;-)
This feels like buildout doing something wrong, at the very least. It
has a
On Fri, Mar 27, 2009 at 16:11, Chris Withers ch...@simplistix.co.uk wrote:
Andreas Jung wrote:
Stop with your approach right now until we have understood what's going
wrong. Working with a SVN checkout from the trunk works (as said).
I'm interested in actually solving what's wrong ;-)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.03.2009 16:11 Uhr, Chris Withers wrote:
Andreas Jung wrote:
Stop with your approach right now until we have understood what's going
wrong. Working with a SVN checkout from the trunk works (as said).
I'm interested in actually solving
Andreas Jung wrote:
One last hint: you might try using 'pip' (instead of 'easy_install').
'pip -v' gives you better information about the dependencies pulled in
and where (but it does not tell you why - at least not obviously).
Engage brain ;-)
I'm not using easy_install, I'm using
On Fri, Mar 27, 2009 at 04:27:31PM -0500, Chris Withers wrote:
Andreas Jung wrote:
One last hint: you might try using 'pip' (instead of 'easy_install').
'pip -v' gives you better information about the dependencies pulled in
and where (but it does not tell you why - at least not obviously).
Paul Winkler wrote:
I'm not using easy_install, I'm using buildout...
(yeah, I know buildout uses easy_install, but...)
One possibility: try using http://pypi.python.org/pypi/gp.recipe.pip ?
I need to be totally upfront about this:
I'm interested in finding out why something that *should*
On Fri, Mar 27, 2009 at 04:34:43PM -0500, Chris Withers wrote:
Paul Winkler wrote:
I'm not using easy_install, I'm using buildout...
(yeah, I know buildout uses easy_install, but...)
One possibility: try using http://pypi.python.org/pypi/gp.recipe.pip ?
I need to be totally upfront about
On Mar 27, 2009, at 4:47 PM, Chris Withers wrote:
Hey All,
I'm trying to get Zope 2.12 working with buildout, in the absence of
docs, I thought I'd try:
[buildout]
parts = zopetest
[zopetest]
recipe = zc.recipe.egg
interpreter = py
eggs =
zope2
...and was rewarded with:
Got
On Mar 27, 2009, at 5:27 PM, Chris Withers wrote:
(yeah, I know buildout uses easy_install, but...)
Not in a significant way. (It uses easy_install to build eggs from
source distributions, and nothing else. It really should use bdist_egg
instead.)
Jim
--
Jim Fulton
Zope Corporation
Paul Winkler wrote:
Well, yeah. The point of the suggestion was specifically to help you
get more info about the dependency chain, since pip is more verbose
about that than easy_install is.
Well, running buildout -v gives some good clues, a piece of which is
this:
Getting required
Chris Withers wrote:
Paul Winkler wrote:
Well, yeah. The point of the suggestion was specifically to help you
get more info about the dependency chain, since pip is more verbose
about that than easy_install is.
Well, running buildout -v gives some good clues, a piece of which is
this:
Hi,
had the same issue tonight. I'm using attached versions.cfg for now.
That works quite well for me.
Cheers,
Tobias
[buildout]
versions = versions
[versions]
Acquisition = 2.12.0a1
DateTime = 2.11.2
ExtensionClass = 2.11.1
Persistence = 2.11.1
tempstorage = 2.11.1
zLOG = 2.11.1
ClientForm
Tobias Rodäbel wrote:
Hi,
had the same issue tonight. I'm using attached versions.cfg for now.
That works quite well for me.
Which issue is this supposed to help with?
Chris
___
Zope-Dev maillist - Zope-Dev@zope.org
On 28.03.2009, at 00:30, Chris Withers wrote:
Tobias Rodäbel wrote:
Hi,
had the same issue tonight. I'm using attached versions.cfg for now.
That works quite well for me.
Which issue is this supposed to help with?
Using zc.buildout. This is my buildut.cfg:
[buildout]
parts = zope zopepy
Tobias Rodäbel wrote:
On 28.03.2009, at 00:30, Chris Withers wrote:
Tobias Rodäbel wrote:
Hi,
had the same issue tonight. I'm using attached versions.cfg for now.
That works quite well for me.
Which issue is this supposed to help with?
Using zc.buildout.
There are currently two
On 28.03.2009, at 00:36, Chris Withers wrote:
There are currently two seperate issue with specifying zope2 as an
egg in a buildout.cfg.
Which of these two issues is your solution designed to address?
My versions.cfg resolved all version conflicts mentioned within this
thread.
Tobias Rodäbel wrote:
My versions.cfg resolved all version conflicts mentioned within this
thread.
Cool, I'll bear it in mind, but right now I want to try and actually fix
things so they work like they should :-)
cheers,
Chris
___
Zope-Dev
39 matches
Mail list logo
