Tres Seaver wrote:
All this derives from my sense that moving our issue collectors to
Launchpad has been only a very minor win:
Yeah, aside from the rather rough around the edge feel to Launchpad's
bug trackers, I'll note that the only way I know to find the relevent
bug tracker is to go to h
Summary of messages to the zope-tests list.
Period Sun Feb 24 12:00:00 2008 UTC to Mon Feb 25 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Sun Feb 24 21:17:21 EST 2008
URL
David Pratt wrote:
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 wa
Hey,
Roger Ineichen wrote:
[snip]
I'm fine with version over develop. It's just another thing
you have to know for sucessfull development. I guess my brain has some
little space for remember such tweaks in buildout ;-)
I'll accept it, but I'm not very happy. It's really an excellent way to
ge
Stephan Richter wrote:
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 c
Christian Theune wrote:
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, th
Hello,
Seem zc.recipe.filestorage has bug in blob-dir
for this buildout config
[var]
recipe = zc.recipe.filestorage
blob-dir = parts/varblobs
zc.recipe.filestorage generates
blob-dir ../parts/varblobs
shared-blob-dir no
path ../parts/var/Data.fs
But 'shared-
Hi,
Martijn Faassen schrieb:
David Pratt wrote:
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.
Hi,
Martijn Faassen schrieb:
Christian Theune wrote:
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
Hi Martijn. I respect the points you make, but disagree with your
comments. Wichert's reply accurately articulates what we are asking
buildout to do. I share this view.
On a personal note, I tend to rely on my own version lists but refer to
the online lists (for support in creating them). On e
Hi Christian
> Betreff: Re: [Zope-dev] Re: buildout 'versions' and 'develop' conflict
[...]
> > I think the explicit versus implicit discussion has no place here.
> > Placing a package on the 'develop' line is a very explicit
> action, and
> > you place it on that line because you want to *de
Hi Martijn
> Betreff: [Zope-dev] Re: AW: buildout 'versions' and 'develop' conflict
[...]
> If people like the current semantics of 'develop' to be "just
> list it on the path", then I propose *another* entry in
> [buildout] that *does* these semantics:
>
> [buildout]
> really_develop =
>
>
12 matches
Mail list logo
