Re: [Repoze-dev] plone 3.1 beta1 eggs

[Reinout van Rees]

Fernando Correa Neto schreef:
 > Hey,
 >
 >> I also have a setup with that approach. I told it to use 3.1 beta1 and
 >> it works like a charm, no problem whatsoever.
 >
 > Did you have any problems with elementtree? repoze.errorlog requires
 >> =1.2.6 and < 1.2.7 but the plone buildout actaully gets a snapshot
 > from 1.2.7 thus causing the version conflict.

Yes. There was a 1.2.7 egg in my buildout egg cache directory that got
used. There are two solutions:

* Switch off the buildout cache (yuck).

* Add "versions = versions" to the [buildout] section of your
buildout.cfg and add the following:

[versions]
elementtree = 1.2.6-20050316


That helped for me. Question is: does repoze.errorlog really need to be
so strict regarding the version?


Reinout


-- 
Reinout van Rees  Blog: http://vanrees.org/weblog/
[EMAIL PROTECTED]  Work: http://zestsoftware.nl/
http://vanrees.org  Video: http://reinout.blip.tv/


___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Re: [Repoze-dev] plone 3.1 beta1 eggs

[Tim Terlegård]

On Mar 13, 2008, at 6:27 PM, Fernando Correa Neto wrote:

>> I also have a setup with that approach. I told it to use 3.1 beta1  
>> and
>> it works like a charm, no problem whatsoever.
>
> Did you have any problems with elementtree? repoze.errorlog requires
>> =1.2.6 and < 1.2.7 but the plone buildout actaully gets a snapshot
> from 1.2.7 thus causing the version conflict.

I'm using this in buildout.cfg:

[buildout]
...
versions = versions

[versions]
elementtree = 1.2.6_20050316

/Tim
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Re: [Repoze-dev] plone 3.1 beta1 eggs

[Fernando Correa Neto]

Hey,

> I also have a setup with that approach. I told it to use 3.1 beta1 and
> it works like a charm, no problem whatsoever.

Did you have any problems with elementtree? repoze.errorlog requires
>=1.2.6 and < 1.2.7 but the plone buildout actaully gets a snapshot
from 1.2.7 thus causing the version conflict.

Regards,
Fernando

>
> (I'm trying out the new repoze.plone egg buildout now, btw).
>
>
> Reinout
>
>
> --
> Reinout van Rees  Blog: http://vanrees.org/weblog/
> [EMAIL PROTECTED]  Work: http://zestsoftware.nl/
> http://vanrees.org  Video: http://reinout.blip.tv/
>
>
>
>
> ___
> Repoze-dev mailing list
> Repoze-dev@lists.repoze.org
> http://lists.repoze.org/listinfo/repoze-dev
>
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Re: [Repoze-dev] plone 3.1 beta1 eggs

[Reinout van Rees]

Tim Terlegård schreef:
> On Mar 12, 2008, at 10:55 PM, Martin Aspeli wrote:
> 
>> I'd love to have some way to test Plone 3.1 beta 1 via Repoze. In  
>> fact,
>> I'd like to move my personal site (blog) over to that setup this  
>> weekend
>> if I can. :)
> 
> 
> It's not the right way to do it, but it works. I tried plone 3.1 beta  
> with repoze
> using the approach in the link below, it works fine (I just did basic  
> stuff). If you
> want to try it right now you can use this approach:
> 
>  http://www.valentinewebsystems.se/2008/02/19/plone-repoze-and-buildout

I also have a setup with that approach. I told it to use 3.1 beta1 and 
it works like a charm, no problem whatsoever.

(I'm trying out the new repoze.plone egg buildout now, btw).


Reinout


-- 
Reinout van Rees  Blog: http://vanrees.org/weblog/
[EMAIL PROTECTED]  Work: http://zestsoftware.nl/
http://vanrees.org  Video: http://reinout.blip.tv/

___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Re: [Repoze-dev] plone 3.1 beta1 eggs

[Carlos de la Guardia]

I have some time on Friday to try this. I'll keep you posted.

Carlos de la Guardia

On Wed, Mar 12, 2008 at 3:18 AM, Chris McDonough <[EMAIL PROTECTED]> wrote:

> Hey Carlos, do you think you might try to get a head start on rolling
> Plone 3.1
> into eggs from the current 3.1 beta?  I don't think we should release a
> repoze.plone that depends on it until it's final, but it would be nice to
> get it
> ready to go.  I'll also need to do some repository shuffling when it comes
> out,
> so we can allow people to use 3.0 still.
>
> Here's what I usually do to make the eggs:
>
> -  I download the Plone tarball.
>
> -  I split it into two pieces: the stuff in the "lib/python" directory
>(this becomes plonelibs) and the stuff in the Products directory
>(this becomes ploneproducts).
>
> - I create a directory containing just the stuff in plonelibs.
>   I add a setup.py to it that looks like this:
>
> # Packaged by Chris McDonough ([EMAIL PROTECTED])
> __version__ = '3.0.6.0'
>
> from ez_setup import use_setuptools
> use_setuptools()
>
> import os
>
> from setuptools import setup, find_packages
> here = os.path.abspath(os.path.dirname(__file__))
> README = open(os.path.join(here, 'README.txt')).read()
>
> setup(name='plonelibs',
>   version=__version__,
>   description='Plone helps you manage your content',
>   long_description=README,
>   keywords='web application server zope plone',
>   author="Plone Foundation and Contributors",
>   author_email="[EMAIL PROTECTED]",
>   url="http://www.plone.org";,
>   license="GPL",
>   packages=find_packages(),
>   include_package_data=True,
>   zip_safe=False,
>   )
>
> - I check in the result.  I check it back out again and run setup.py sdist
>   to create the source distro.
>
> - I create a directory named ploneproducts.  I put a Products directory in
>   it that has a namespace declaration in its __init__.py.  I put
>   the following products in it:
>
> ATContentTypesCMFTestCase  PloneTestCase
> ATReferenceBrowserWidget  ExtendedPathIndexPloneTranslations
> AdvancedQuery ExternalEditor   PortalTransforms
> ArchetypesGroupUserFolder  ResourceRegistries
> CMFDiffTool   Marshall SecureMailHost
> CMFDynamicViewFTI MimetypesRegistryZopeVersionControl
> CMFEditions   NuPlone
> CMFFormController PasswordResetToolkupu
> CMFPlacefulWorkflow   PlacelessTranslationService  statusmessages
> CMFPlone  PloneLanguageToolvalidation
> CMFQuickInstallerTool PlonePAS
>
>  (the other products come from cmflib/PAS/GenericSetup eggs)
>
> - I create a setup.py in the root of ploneproducts that looks like this:
>
> # Packaged by Chris McDonough ([EMAIL PROTECTED])
> __version__ = '3.0.6.0'
>
> from ez_setup import use_setuptools
> use_setuptools()
>
> import os
>
> from setuptools import setup, find_packages
> here = os.path.abspath(os.path.dirname(__file__))
> README = open(os.path.join(here, 'README.txt')).read()
>
> setup(name='ploneproducts',
>   version=__version__,
>   description='Zope Product packages for Plone',
>   long_description=README,
>   keywords='web application server zope plone',
>   author="Plone Foundation and Contributors",
>   author_email="[EMAIL PROTECTED]",
>   url="http://www.plone.org";,
>   license="GPL",
>   packages=find_packages(),
>   include_package_data=True,
>   namespace_packages=['Products'],
>   zip_safe=False,
>   install_requires=[
>  'plonelibs >= 3.0.1.0',
>  'Products.PluginRegistry == 1.1.2',
>  'Products.PluggableAuthService == 1.5.3',
>  'PIL >= 1.1.6',
>  'elementtree >=1.2.6, < 1.2.7',
>  ],
>   dependency_links=['http://dist.repoze.org'
> ],
>   )
>
> - I check in the result, then check it back out again and
>   run setup.py sdist in the checkout to generate the source
>   distro.
>
> - I bump the repoze.plone version and roll another release of it.
>   Its setup.py looks like this:
>
> __version__ = '0.2.8'
>
> from ez_setup import use_setuptools
> use_setuptools()
>
> import os
>
> from setuptools import setup, find_packages
>
> here = os.path.abspath(os.path.dirname(__file__))
> README = open(os.path.join(here, 'README.txt')).read()
>
> setup(name='repoze.plone',
>   version=__version__,
>   description=('A metapackage that allows installation of Plone 3'
>'within a repoze environment'),
>   long_description=README,
>   classifiers=[
> "Development Status :: 1 - Planning",
> "Intended Audience :: Developers",
> "Programming Language :: Python",
> "Framework :: Plone",
> "Topic :: Internet :: WWW/HTTP",
> "Topic :: Internet :: WWW/HTTP :: Dynamic Content",
>

Re: [Repoze-dev] plone 3.1 beta1 eggs

[Tim Terlegård]

On Mar 12, 2008, at 10:55 PM, Martin Aspeli wrote:

> I'd love to have some way to test Plone 3.1 beta 1 via Repoze. In  
> fact,
> I'd like to move my personal site (blog) over to that setup this  
> weekend
> if I can. :)


It's not the right way to do it, but it works. I tried plone 3.1 beta  
with repoze
using the approach in the link below, it works fine (I just did basic  
stuff). If you
want to try it right now you can use this approach:

 http://www.valentinewebsystems.se/2008/02/19/plone-repoze-and-buildout

After I wrote that blog I also had to write a cleanrunzope.py script  
because  the
instance recipe creates a runzope script with lots of egg added to  
PYTHONPATH.
So this script is run by buildout (like with the addpath.py script)  
and cleans up
runzope.

I know it's hacky, but like you I wanted to use repoze, deliverance  
etc _now_.
It works. If you want the cleanrunzope.py script I can send it to you.

/Tim
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

Re: [Repoze-dev] plone 3.1 beta1 eggs

[Martin Aspeli]

Chris McDonough wrote:
> Hey Carlos, do you think you might try to get a head start on rolling Plone 
> 3.1 
> into eggs from the current 3.1 beta?  I don't think we should release a 
> repoze.plone that depends on it until it's final, but it would be nice to get 
> it 
> ready to go.  I'll also need to do some repository shuffling when it comes 
> out, 
> so we can allow people to use 3.0 still.

I'd love to have some way to test Plone 3.1 beta 1 via Repoze. In fact, 
I'd like to move my personal site (blog) over to that setup this weekend 
if I can. :)

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev

[Repoze-dev] plone 3.1 beta1 eggs

[Chris McDonough]

Hey Carlos, do you think you might try to get a head start on rolling Plone 3.1 
into eggs from the current 3.1 beta?  I don't think we should release a 
repoze.plone that depends on it until it's final, but it would be nice to get 
it 
ready to go.  I'll also need to do some repository shuffling when it comes out, 
so we can allow people to use 3.0 still.

Here's what I usually do to make the eggs:

-  I download the Plone tarball.

-  I split it into two pieces: the stuff in the "lib/python" directory
(this becomes plonelibs) and the stuff in the Products directory
(this becomes ploneproducts).

- I create a directory containing just the stuff in plonelibs.
   I add a setup.py to it that looks like this:

# Packaged by Chris McDonough ([EMAIL PROTECTED])
__version__ = '3.0.6.0'

from ez_setup import use_setuptools
use_setuptools()

import os

from setuptools import setup, find_packages
here = os.path.abspath(os.path.dirname(__file__))
README = open(os.path.join(here, 'README.txt')).read()

setup(name='plonelibs',
   version=__version__,
   description='Plone helps you manage your content',
   long_description=README,
   keywords='web application server zope plone',
   author="Plone Foundation and Contributors",
   author_email="[EMAIL PROTECTED]",
   url="http://www.plone.org";,
   license="GPL",
   packages=find_packages(),
   include_package_data=True,
   zip_safe=False,
   )

- I check in the result.  I check it back out again and run setup.py sdist
   to create the source distro.

- I create a directory named ploneproducts.  I put a Products directory in
   it that has a namespace declaration in its __init__.py.  I put
   the following products in it:

ATContentTypesCMFTestCase  PloneTestCase
ATReferenceBrowserWidget  ExtendedPathIndexPloneTranslations
AdvancedQuery ExternalEditor   PortalTransforms
ArchetypesGroupUserFolder  ResourceRegistries
CMFDiffTool   Marshall SecureMailHost
CMFDynamicViewFTI MimetypesRegistryZopeVersionControl
CMFEditions   NuPlone
CMFFormController PasswordResetToolkupu
CMFPlacefulWorkflow   PlacelessTranslationService  statusmessages
CMFPlone  PloneLanguageToolvalidation
CMFQuickInstallerTool PlonePAS

  (the other products come from cmflib/PAS/GenericSetup eggs)

- I create a setup.py in the root of ploneproducts that looks like this:

# Packaged by Chris McDonough ([EMAIL PROTECTED])
__version__ = '3.0.6.0'

from ez_setup import use_setuptools
use_setuptools()

import os

from setuptools import setup, find_packages
here = os.path.abspath(os.path.dirname(__file__))
README = open(os.path.join(here, 'README.txt')).read()

setup(name='ploneproducts',
   version=__version__,
   description='Zope Product packages for Plone',
   long_description=README,
   keywords='web application server zope plone',
   author="Plone Foundation and Contributors",
   author_email="[EMAIL PROTECTED]",
   url="http://www.plone.org";,
   license="GPL",
   packages=find_packages(),
   include_package_data=True,
   namespace_packages=['Products'],
   zip_safe=False,
   install_requires=[
  'plonelibs >= 3.0.1.0',
  'Products.PluginRegistry == 1.1.2',
  'Products.PluggableAuthService == 1.5.3',
  'PIL >= 1.1.6',
  'elementtree >=1.2.6, < 1.2.7',
  ],
   dependency_links=['http://dist.repoze.org'],
   )

- I check in the result, then check it back out again and
   run setup.py sdist in the checkout to generate the source
   distro.

- I bump the repoze.plone version and roll another release of it.
   Its setup.py looks like this:

__version__ = '0.2.8'

from ez_setup import use_setuptools
use_setuptools()

import os

from setuptools import setup, find_packages

here = os.path.abspath(os.path.dirname(__file__))
README = open(os.path.join(here, 'README.txt')).read()

setup(name='repoze.plone',
   version=__version__,
   description=('A metapackage that allows installation of Plone 3'
'within a repoze environment'),
   long_description=README,
   classifiers=[
 "Development Status :: 1 - Planning",
 "Intended Audience :: Developers",
 "Programming Language :: Python",
 "Framework :: Plone",
 "Topic :: Internet :: WWW/HTTP",
 "Topic :: Internet :: WWW/HTTP :: Dynamic Content",
 "Topic :: Internet :: WWW/HTTP :: WSGI",
 "Topic :: Internet :: WWW/HTTP :: WSGI :: Application",
 ],
   keywords='web application server wsgi zope plone',
   author="Agendaless Consulting",
   author_email="[EMAIL PROTECTED]",
   dependency_links=['http://dist.repoze.org'],
   url="http://www.repoze.org";,
   license="BSD-derived (ht