[Zope-CMF] Re: Eggification redux
-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 likely that it has to get a different version of Y. The result is a version conflict. This could also easily be fixed with a working set that dictates which versions would be used from the beginning. >>> IN the long run, this would be better served by a better algorithm >>> for constructing setuptools working sets. >> ... which would require having access to the dependency data before >> installation. > > No, not really, at least not in buildout's case. It's really not > that big a deal to download a distribution that you ultimately don't > use. If we can keep setuptools from prematurely installing downloaded eggs, sure; at the moment, it is trivial to get setuptools into a "false conflict" situaltion, because it processes dependencies incrementally, rather than solving the "transitive closure" of the graph before attempting to install anything. > I agree it might be better if the index made dependency data >> available. Not exposing the dependency information in the index seems like a missing-feature-is-really-a-bug to me. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+RLj+gerLs4ltQ4RAobUAJ9Fj52kb9SqHJ5rbYVNCkxUr0XRZACeKNs2 kTPVmL+rwbYixYDCm/X1LIc= =1WIX -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: Eggification redux
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 > '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 other thoughts? > >>> While I am very sceptical about the move to eggs (I know it's > >>> inevitable) and I hope we can avoid some of the problems that seem > >>> to be affecting Grok as a result. > >> Grok's problems are primarily related to the lack of a working set > >> definition for Zope 3. > > > > I don't know what you mean by this. > > 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 well together, is the only > way out of this issue. E.g., a URL like: > > http://pypi.python.org/pypi/release/zope3.4 > > would be usable as an 'index-url' for setuptools: when used this way, > setuptools would only find / install eggs from the "gardened" set, > rather than whatever anyone happened to have uploaded that day. > > If PyPI can't be tweaked to provide such a feature, we may need to come > up with some kind of mirroring scheme which does allow it. +1 It's the same problem Linux distributions have solved in their package managers. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Eggification redux
-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 '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 other thoughts? >>> While I am very sceptical about the move to eggs (I know it's >>> inevitable) and I hope we can avoid some of the problems that seem >>> to be affecting Grok as a result. >> Grok's problems are primarily related to the lack of a working set >> definition for Zope 3. > > I don't know what you mean by this. 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 well together, is the only way out of this issue. E.g., a URL like: http://pypi.python.org/pypi/release/zope3.4 would be usable as an 'index-url' for setuptools: when used this way, setuptools would only find / install eggs from the "gardened" set, rather than whatever anyone happened to have uploaded that day. If PyPI can't be tweaked to provide such a feature, we may need to come up with some kind of mirroring scheme which does allow it. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+PWv+gerLs4ltQ4RApd3AKCNANKTREE+1V7MJEexRgwNZl0DSwCfTTdL W5IG3LF2jjLbYnVTl1/6+YA= =GlfL -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Eggification redux
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 objections, or other thoughts? While I am very sceptical about the move to eggs (I know it's inevitable) and I hope we can avoid some of the problems that seem to be affecting Grok as a result. Grok's problems are primarily related to the lack of a working set definition for Zope 3. We badly need it, not only for Zope 3 proper but also for projects which consume Zope 3 eggs (probably Zope 2 in the future, but naturally also grok). +1 to the eggification -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Eggification redux
Tres Seaver wrote:
> SVN Reorganiztion
> -
>
> I just worked a bit today on spliting CMF 2.1.0 (GenericSetup 1.3.2) out
> into separately releasable egg-based distributions. For the initial
> pass, see:
>
> svn://svn.zope.org/repos/main/Products.GenericSetup/tags/1.3.2
>
> Note that the SVN URL above is not the same as the one we've been using
> (svn://svn.zope.org/repos/main/GenericSetup) and that it adds the
> additional "namespace" package ('Products') to the checkout.I plan
> to fix up the externals currenly pointing into '/GenericSetup' in the
> CMF trunk and 2.1 branch, and then make '/GenericSetup' empty, with a
> pointer to the new location.
>
> Egg Releases
>
>
> I uploaded the Products.GenericSetup 1.3.2 egg to the Cheeseshop:
>
> http://pypi.python.org/pypi/Products.GenericSetup
>
> The egg should be 'easy_installable' in any environment with setuptools
> installed; if that environment has a properly-namespaced 'Products'
> package (Zope2 trunk, or with the backport I'm proposing for Zope issue
> #2359), it should Just Work.
>
> Further Work
>
>
> 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 other thoughts?
Big +1 :)
Hanno
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
