for info, this is into the buildout now.
Lucie
-- 
S i x  F e e t  U p ,  I n c .  |  http://www.sixfeetup.com
Phone: +1 (317) 861-5948 x605
mailto:[EMAIL PROTECTED]
REGISTER NOW for the Plone Deployment Workshop | Nov. 20-21, 2008
http://www.sixfeetup.com/news/plone-deployment-workshop



On Mon, Aug 25, 2008 at 10:06 AM, Lucie Lejard <[EMAIL PROTECTED]> wrote:
> I am all for it. We already do that in all our buildout and this is
> really useful.
> Let me know if you are going to include it into the buildout or else
> I'll do it probably next Friday.
>
> Lucie
>
> --
> S i x F e e t U p , I n c . | "Nowhere to go but open source"
> Silicon Valley: +1 (650) 401-8579 x605
> Midwest: +1 (317) 861-5948 x605
> Toll-Free: 1-866-SIX-FEET
> mailto:[EMAIL PROTECTED]
> http://www.sixfeetup.com | Zope/Plone Custom Development
>
>
>
> On Sun, Aug 24, 2008 at 10:47 PM, Matt Halstead <[EMAIL PROTECTED]> wrote:
>>
>> Some packages in the PloneGetPaid buildout reference zope.* eggs in
>> their setup.py. In these cases it is nice to add fake-zope-eggs = true
>> into the [zope2] section of the buildout so that setuptools uses the
>> eggs that comes with that zope instance and doesn't try to pull
>> separate copies of these, and potentially incompatible versions since
>> the versions are not pinned in these dependency references.
>>
>> So I am suggesting the following for the zope2 part
>>
>> [zope2]
>> recipe = plone.recipe.zope2install
>> url = ${plone:zope2-url}
>> fake-zope-eggs = true
>>
>> cheers
>> Matt
>>
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"getpaid-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to