Adam Groszer wrote:
Hello Philipp,
Friday, October 6, 2006, 9:06:39 AM, you wrote:
I'm suspecting that Adam, who built the 3.2.x releases, was executing
the wrong command when building the tarball, because zope.conf.in on the
3.2.x branch doesn't contain the formatter line. It's zope.conf.in on
the 3.3.x branch that does.
Yeah, now I'm even more puzzled. Indeed there is nowhere a formatter line
in any zope.conf.in, but in the
\svn_zope_322\Zope-win-3.2.2\Dependencies\Zope-src-Zope-win-3.2.2\Zope-src\zopeskel\etc\zope.conf.in
(after the build)
I'm still trying to figure out how it comes.
See Entry #4 on http://www.zope.org/Collectors/Zope3-dev/719
but of course you need to replace Zope-3.3.0b1 with the current tag
(which is 3.2.2). My suspicion is that Adam forgot to do that and so he
built a tarball of 3.2.2, but with zopeskel from 3.3.x.
I'm sorry, but I did it. But the required command is not exactly the
same.
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZopeWindowsRelease
says that I should run
python ..\zpkg\bin\zpkg -C releases\Zope.cfg -v 3.1.0c1 -t Zope-win
It looks like the instructions aren't complete here. You should be
specifying -r 3.2.2 here so that it looks at the tag.
Philipp
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
