Drop plone.recipe.precompiler?
Closed this issue · 4 comments
If used with a combined policy / buildout where the policy is checked out from source, and used with develop = ., the use of plone.recipe.precompiler will cause the entire deployment directory being scanned during buildout, including directories like var/.
If var/ contains a blobstorage with a ton of files, this will slow down buildout to the point where it basically won't finish.
So, can we drop plone.recipe.precompiler from production.cfg? I don't quite see the point of it anyway: One reason for its existence it is to avoid writes during application lifetime to code directories, but this point is void anyway if we're keeping var/ inside a Python development egg.
@jone @maethu @buchi can we remove this? Or what was the original motivation for including it?
One reason for its existence it is to avoid writes during application lifetime to code directories, but this point is void anyway if we're keeping var/ inside a Python development egg.
I think the goal is to not write to the (shared?) egg cache.
I think we've started using it because we actually had no / wrong / not updated translations in some situations, which is quite bad, also because we wouldn't notice.
I have no problem with stop using it / removing from production.cfg if we are sure that the user still has always the current translations.
@jone
I'm guessing that zope_i18n_compile_mo_files true for the Zope-Instance wasn't set then:
http://vincentfretin.ecreall.com/articles/my-translation-doesnt-show-up-in-plone-4
We've got that in production.cfg now though.
Go ahead, gonna put it back if necessary 😜