Am 25.09.2007 um 02:05 schrieb Tres Seaver:
I'd like to break the remaining CMF packages out (moving from '/
CMF' to
'Products.CMFCore', 'Products.CMFDefault', etc.) and push the 2.1.0
eggs
out, as well as equivalent changes for PluggableAuthService and
PluginRegistry.
Any objections, or ot
Charlie Clark wrote:
Am 25.09.2007 um 02:05 schrieb Tres Seaver:
I'd like to break the remaining CMF packages out (moving from '/CMF' to
'Products.CMFCore', 'Products.CMFDefault', etc.) and push the 2.1.0 eggs
out, as well as equivalent changes for PluggableAuthService and
PluginRegistry.
Any
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
tseaver
- "CMF needs View-based TypeInformation",
[Accepted] http://www.zope.org/Collectors/CMF/437
- "CachingPolicyManager awareness of File and
Hi,
I've been on vacation I took my time answering.
Rob Miller, on 2007-09-06:
> okay, here's where things get off track. in GenericSetup, there is no such
> thing (yet, perhaps) as an "upgrade profile". it's possible to define an
> extension profile and to USE it as part of an upgrade proces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> On Sep 25, 2007, at 3:40 AM, Philipp von Weitershausen wrote:
>
>> Charlie Clark wrote:
>>> Am 25.09.2007 um 02:05 schrieb Tres Seaver:
I'd like to break the remaining CMF packages out (moving from '/
CMF' to
'Pro
On 25 Sep 2007, at 13:20 , Jim Fulton wrote:
On Sep 25, 2007, at 3:40 AM, Philipp von Weitershausen wrote:
Charlie Clark wrote:
Am 25.09.2007 um 02:05 schrieb Tres Seaver:
I'd like to break the remaining CMF packages out (moving from '/
CMF' to
'Products.CMFCore', 'Products.CMFDefault', etc.)
Summary of messages to the cmf-tests list.
Period Mon Sep 24 12:00:00 2007 UTC to Tue Sep 25 12:00:00 2007 UTC.
There were 11 messages: 11 from CMF Unit Tests.
Tests passed OK
---
Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux
From: CMF Unit Tests
Date: Mon Sep 24 21:25:48 EDT 2
Previously Philipp von Weitershausen wrote:
> On 25 Sep 2007, at 13:20 , Jim Fulton wrote:
> >On Sep 25, 2007, at 3:40 AM, Philipp von Weitershausen wrote:
> >
> >>Charlie Clark wrote:
> >>>Am 25.09.2007 um 02:05 schrieb Tres Seaver:
> I'd like to break the remaining CMF packages out (moving fr
Previously Tres Seaver wrote:
> Jim Fulton wrote:
> > On Sep 25, 2007, at 3:40 AM, Philipp von Weitershausen wrote:
> >
> >> Charlie Clark wrote:
> >>> Am 25.09.2007 um 02:05 schrieb Tres Seaver:
> I'd like to break the remaining CMF packages out (moving from '/
> CMF' to
> 'Produc
(Also CCing zope3-dev where the first known working set discussion
started a while ago)
Tres Seaver wrote:
This is the "known good" problem. I'm pretty convinced that adding some
kind of "PyPI subset", where gardeners for a given "package set" keep
the list of packages / versions known to work
On 25 Sep 2007, at 14:06 , Jim Fulton wrote:
There are several problems.
* We've had to nail some of the versions because buildout was
being a bit over-zealous when getting eggs on Windows. It would
take the newest egg, despite the fact that other eggs had binary
releases. I guess that's n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(CC'ing the Python distutils list, which is where setuptools development
is discussed; maybe I should be including the catalog-sig too, but I
don't read that list).
Philipp von Weitershausen wrote:
> (Also CCing zope3-dev where the first known workin
Am 25.09.2007 um 14:06 schrieb Philipp von Weitershausen:
* A versions.cfg that's loaded via HTTP. zc.buildout actually
supports this now which makes it quite appealing. Also, far as I
know, all major deployers of Zope3 that use zc.buildout for
deployment use this form of pinning egg versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
* When package A depends on Y and package B also depends on Y,
but with some version restrictions, buidout will first try to get
the newest version of Y when installing A. But then when
installing B, it is l
Tres Seaver wrote:
[snip]
This is certainly an interesting approach. I'd be curious how you would
garden this known working set. Martijn makes a pretty good case for
maintaining such working sets close to the package in question (e.g. the
grok egg, the Plone egg, etc.).
I would argue that thi
Martijn Faassen wrote at 2007-9-25 17:22 +0200:
> ...
>Should we then encourage everyone to hardcode version numbers in their
>setup.py's dependencies list?
I think this goes against building applications from components --
as it drastically increases the probability of conflicts.
Components shou
On 9/25/07, Maurits van Rees <[EMAIL PROTECTED]> wrote:
> When you want to remove an index or column you can do that by editing
> the profile and adding remove="True" to that index or column. So this
> upgrade can be represented as a profile edit. But applying the
> profile will empty the remaini
17 matches
Mail list logo
