yuppie wrote:
And it doesn't work on Windows.
Have you tried it?
...if you had, you would have noticed that the Win32 service stuff as
broken, even without using buildout.
No. I did have tried with mkzopeinstance and zopeservice.py. And it did
work for me.
I'm surprised. It certainly
Hi Chris!
Chris Withers wrote:
(updating myself much much later)
(replying much much later)
Chris Withers wrote:
yuppie wrote:
You ripped my sentence out of context. We were talking about Zope
2.12. And Zope 2.12 currently doesn't use buildout for setting up
instances.
Sure it does.
(updating myself much much later)
Chris Withers wrote:
yuppie wrote:
You ripped my sentence out of context. We were talking about Zope
2.12. And Zope 2.12 currently doesn't use buildout for setting up
instances.
Sure it does. I've published the recipe. There's no more needed than
that...
yuppie wrote:
You ripped my sentence out of context. We were talking about Zope 2.12.
And Zope 2.12 currently doesn't use buildout for setting up instances.
Sure it does. I've published the recipe. There's no more needed than that...
Your recipe is not published as part of Zope 2.12.
I'm
yuppie wrote:
yuppie wrote:
Currently buildout is just used to set up the software.
Wrong. The buildout I posted, which uses no fancy recipes, sets up an
instance. The egg cache, as such, is the software...
You ripped my sentence out of context. We were talking about Zope 2.12.
And
Hi Chris!
Chris Withers wrote:
yuppie wrote:
yuppie wrote:
Currently buildout is just used to set up the software.
Wrong. The buildout I posted, which uses no fancy recipes, sets up an
instance. The egg cache, as such, is the software...
You ripped my sentence out of context. We were
Hi Chris!
Chris Withers wrote:
yuppie wrote:
Currently buildout is just used to set up the software.
Wrong. The buildout I posted, which uses no fancy recipes, sets up an
instance. The egg cache, as such, is the software...
You ripped my sentence out of context. We were talking about
Hello,
On Fri, Aug 14, 2009, Jim Fulton wrote:
On Fri, Aug 14, 2009 at 12:30 PM, Jonas Meurer jo...@freesources.org wrote:
...
zope2 releases based on buildout make it very hard for distributors to
package zope2. especially as zope2 requires
from what i know about buildout (and that's not
On 24/08/2009 Chris Withers wrote:
that's important for distributors who want to distribute generic
software, not user specific instance setups.
Distributors just want a tarball or similar, let them use
zc.sourcerelease and have a slightly different buildout.cfg, or even
default.cfg,
yuppie wrote:
Currently buildout is just used to set up the software.
Wrong. The buildout I posted, which uses no fancy recipes, sets up an
instance. The egg cache, as such, is the software...
is used to set up instances. And while I see that using buildout for
setting up everything in one
Hi Chris!
Chris Withers wrote:
yuppie wrote:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless buildout as the way to set up Zope 2.12,
then mkzopeinstance becomes moot.
Not everybody agrees with that. But nevertheless, both
On 14/08/2009 Jim Fulton wrote:
On Fri, Aug 14, 2009 at 12:30 PM, Jonas Meurerjo...@freesources.org wrote:
...
zope2 releases based on buildout make it very hard for distributors to
package zope2. especially as zope2 requires
from what i know about buildout (and that's not much), it either
yuppie wrote:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless buildout as the way to set up Zope 2.12,
then mkzopeinstance becomes moot.
Not everybody agrees with that. But nevertheless, both approaches can
learn from each
On 14/08/2009 Chris Withers wrote:
yuppie wrote:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless buildout as the way to set up Zope 2.12,
then mkzopeinstance becomes moot.
Not everybody agrees with that. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Meurer wrote:
zope2 releases based on buildout make it very hard for distributors to
package zope2. especially as zope2 requires
from what i know about buildout (and that's not much), it either requires
a working internet connection or a
Tres Seaver wrote:
Sorry, we aren't making such tarballs any longer. Distributors who
don't want to package the broken-out eggs separately will need to
synthesize such a beast, perhaps using something like 'zc.sourcerelease'.
I was just about to suggest this. I haven't used it, but my
On Fri, Aug 14, 2009 at 12:30 PM, Jonas Meurerjo...@freesources.org wrote:
...
zope2 releases based on buildout make it very hard for distributors to
package zope2. especially as zope2 requires
from what i know about buildout (and that's not much), it either requires
a working internet
Hi Chris!
Chris Withers wrote:
yuppie wrote:
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless
yuppie wrote:
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
I wish we could just bless buildout as the way to set up Zope
Andreas Jung wrote:
On 23.07.09 12:10, yuppie wrote:
Any thoughts? Is the 2.12 branch still open for changes like that?
Go ahead. I also had to fix a similar issue some days ago inside
Zope startup code.
Done.
http://svn.zope.org/?rev=102230view=rev
http://svn.zope.org/?rev=102231view=rev
On 7/23/09 12:10 PM, yuppie wrote:
Hi!
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
Therefore mkzopeinstance now
On 23.07.09 12:10, yuppie wrote:
Hi!
SOFTWARE_HOME no longer exist in Zope 2.12, all the software is now
somewhere on sys.path.
So this no longer works in zopectl:
ZDCTL=$SOFTWARE_HOME/Zope2/Startup/zopectl.py
exec $PYTHON $ZDCTL -C $CONFIG_FILE $@
Therefore mkzopeinstance now creates
22 matches
Mail list logo
