Encolpe Degoute a écrit :
> Jean-Michel FRANCOIS a écrit :
>
>> Hi,
>>
>> I m not sure to be on the good ML. So don't hesitate to forward.
>>
>> I have tryed many ways of making release. At the moment I'm using
>> buildout with private pypi + pypi.
>>
>> I would like to make a unified installer for a project.
>>
>> So, do you have scripts to help you to create the unified installer ?
>>
>> What is the process to start from the code and have *.egg 'folders' ?
>>
>
> collective.releaser can build your whole project for masosx, linux and
> windows.
> You just have to run project_release
>
>
I have take a look at collective.releaser. It is very interesting, but
doesn't work:
project_deploy
buildout.cfg
Traceback (most recent call
last):
File "/home/toutpt/workspace/buildout/bin/project_deploy", line 7, in
?
sys.exit(
File
"/home/toutpt/workspace/buildout/lib/python2.4/site-packages/collective.releaser-0.6.4-py2.4.egg/collective/releaser/base.py",
line 62, in
_savewd
return function(*args,
**kw)
File
"/home/toutpt/workspace/buildout/lib/python2.4/site-packages/collective.releaser-0.6.4-py2.4.egg/collective/releaser/project.py",
line 429, in
deploy_release
if len(argv) !=
1:
NameError: global name 'argv' is not defined
The documentation look like to answer my need:
"""This will build a tarball in /tmp using VirtualEnv, and set
everything up so the buildout can be reinstalled offline anywhere with
this archive."""
Thank you to point this me out.
--
Jean-Michel FRANCOIS
Makina-Corpus
_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup
