Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago There are no version pegs for Plone and Portal
TO DO :
add version pegs for Plone and PortalOriginal comment by ashok.ha...@gmail.com on 18 Mar 2010 at 6:47
GoogleCodeExporter
commented
9 years ago Plone buildout setups its own version configuration
use
http://pypi.python.org/pypi/buildout.dumppickedversions to find missing version
pegs ...
Original comment by ashok.ha...@gmail.com on 18 Mar 2010 at 8:03
GoogleCodeExporter
commented
9 years ago http://code.google.com/p/bungeni-portal/source/detail?r=6336
http://code.google.com/p/bungeni-portal/source/detail?r=6335
Above are the correct version pegs for the plone buildout - plone builds out and
starts up - currently there are 244 version pegs
-- lxml has been left out of the version pegs -because the system seems to
depend on
2 different versions of lxml - 2.1.2 and 2.2. so the peg in buildout.cfg has
been
left in for 2.1.2 and the 2.2 has been left as the latest version on the package
index (since specifying it in versions.cfg causes a clash with the version
specified
in buildout.cfg).
-- ore.recipe.staticlxml - this has been pegged to 0.5 - however there is some
configuration missing from this recipe wherein despite statically building
libxslt
and libxml2 it uses the system libxml2 and libxslt (this is how it current
happens -
and is a potential source of major problem). It needs to be tested with a
version of
lxml that works with the static build of libxml2 and libxslt.
-- quintagroup static portlet has not been version pegged
Original comment by ashok.ha...@gmail.com on 26 Mar 2010 at 3:00
GoogleCodeExporter
commented
9 years ago The system does not depend on 2 different versions of lxml. It only depends on
an
lxml version that is >= 2.1.1. This requirement comes from chameleon.html.
The z3c.recipe.staticlxml (0.5) default settings work fine and builds lxml
statically
against the libxml2, libxlst libraries.
NB:There should only be one version pin for lxml.
Pegging lxml to two different versions was the cause of the conflict:
buildout.cfg had this entry:
[lxml]
recipe = z3c.recipe.staticlxml
egg = lxml==2.1.2
whilst versions.cfg had this entry:
lxml = 2.2.6
.
The version peg has been moved out of buildout.cfg and into versions.cfg.
Original comment by mng...@gmail.com on 12 Apr 2010 at 11:17
GoogleCodeExporter
commented
9 years ago TODO --
fix local dependencies for lxml on bungeni and portal buildoutsOriginal comment by ashok.ha...@gmail.com on 4 May 2010 at 7:29
GoogleCodeExporter
commented
9 years ago Task completed
-- versions pegged for bungeni/plone/portal
-- tagging of successful tested builds
-- externals are pegged to specific revisions
-- libxml2/libxslt dependencies have been localized to the builds
Original comment by ashok.ha...@gmail.com on 12 May 2010 at 11:21
Original issue reported on code.google.com by
ashok.ha...@gmail.comon 17 Mar 2010 at 10:03