AW: [Zope-dev] buildout 'versions' and 'develop' conflict

[Roger Ineichen]

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 between two 
> explicit configurations that are potentially conflicting.
> 
> There can be arguments for giving priority on one of them.
> Maybe the best thing here would be to just warn the user (in 
> stdout) about the conflict. Buildout should tell him that 
> either the specified version won't be used, or the 
> develop-egg won't be used.

For me it's simple, I like to define develop packages 
and I'm confused if this eggs are not used. I never develop 
on different versions? Does anybody need to develop on 
versions? If so this is the only reason why version 
should affect develop configuration.

I really don't understand what development has to do with
versions at all. If I develop a egg, I link then into the 
develop folder because I need that egg as a new develop dependency
because it offers a new version which is not availble in any version
or somewhere except in the repository.

Add additional configuration into the buildout is just overhead.

Can somebody give me a use-case why version should have more priority
then explicit linked in develop eggs?

And if it comes to explicit over implicit. I explicit define
a develop egg for development and it implicit uses the KGS
defined as a default configuration. There is no explicit
version which I define in the develoment process. Versions are 
just there or not.

This means explicit develop egg links get overriden by implicit 
version definitions. I think that's the only thing which we get
confused and discuss this topic now. right?

Or are I'm wrong?

Hm, or do we have different point of views here and we argument in a
different context. Is there a different point of preferred behavoir
if we develop OR setup an application based on builldout?

My argumentation is only based on the development point of view.
I'm not sure if this will affect an application setup for production
use. I'm also not sure what Jim means with "Ubuntu and system Python".

but anyway, 
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 ;-)

Regards
Roger Ineichen

> regards
> Christophe
> 
> 
> > 
> > Regards,
> > David
> > 
> > 
> > Jim Fulton wrote:
> >>
> >> 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, 
> >>> so when defining a develop-egg, you clearly indicate that you want
> >>> *that* path, whathever version this develop-egg defines.
> >>
> >> That is the philosophy that buildout takes. That's why, 
> when picking 
> >> versions, buildout prefers develop eggs over newer 
> non-develop eggs.
> >> However, buildout will only use a develop egg if it 
> satisfies stated 
> >> requirements.  As it stands today, specifying a version in 
> a versions 
> >> section is like stating a == requirement in a setup script or in a 
> >> eggs option.
> >>
> >> Jim
> >>
> >> --
> >> Jim Fulton
> >> Zope Corporation
> >>
> >>
> >> _______________________________________________
> >> Zope-Dev maillist  -  Zope-Dev at zope.org 
> >> http://mail.zope.org/mailman/listinfo/zope-dev
> >> **  No cross posts or HTML encoding!  ** (Related lists 
> >> -http://mail.zope.org/mailman/listinfo/zope-announce
> >> http://mail.zope.org/mailman/listinfo/zope )
> >>
> > 
> > 
> 
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  ** (Related lists -  
> http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope )
>