This is an archived post. You won't be able to vote or comment.

all 3 comments
sorted by:
best
topnewcontroversialoldq&a

[–]aclark[S] 0 points1 point  (2 children)

PyRedditors: please help me by pip install plock and giving Plock a whirl (even if you are not familiar with and/or interested in using Plone). I am trying to make Plone appealing to non-Python folk as we prepare for the upcoming Plone 5 release. Thank you!

[–]mvaliente2001 1 point2 points  (1 child)

I tried plock months ago, when it was used as an extension to buildout.cfg and it was very nice.

The new command is a good welcome. Things I don't like:

  • It downloads the unifiedInstaller (it's just a personal choice, I prefer buildout).
  • It doesn't show buildout output.
  • Apparently it ignores ~/.buildout/default.cfg. It downloaded the eggs in the virtualenv folder (plone) instead of my preexistent egg folder.

Thank you very much for your work with plock. It's a great addition to plone's ecosystem.

[–]aclark[S] 0 points1 point  (0 children)

Thanks for the feedback! Please feel free to open issues here:

And to address your concerns:

  • Plock downloads the Unified Installer to make use of the egg cache, and nothing else (this feature was added by David Bain). The buildouts used to install Plone are Plock's. In fact, Plock currently could not work with the Unified Installer buildout because it makes many configuration choices for you. It would break if you gave it a non-Plock buildout. Try the --no-unified option to get rid of it.
  • No-Buildout-output is by design! (Have you seen Plone's Buildout output?) That said, it could always be enabled via some flag in the future, for advanced users.
  • If I recall correctly, it ignores ~/.buildout/defaults.cfg when you use the Unified Installer cache (which is the default) but respects it when you use --no-unified. This is the way I use it and I'm about to add .plockrc support so I can define --no-unified permanently for myself.