Wipes out Extensions and etc folders on each run
Bug #946865 reported by
sureshvv
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| collective.buildout |
Opinion
|
Undecided
|
Unassigned | ||
Bug Description
If I just want to add an egg, I run the risk of losing my Extensions folder and hand crafted changes to zope.conf.
Should we keep Extensions and etc folders outside of parts so that they don't get wiped out each time buildout is run?
We can symlinks from the parts folders to the real locations.
We can have an option to regenerate the zope.conf, site.zcml etc. when needed.
If people think this is a good idea, I will volunteer to implement.
Revision history for this message
| Hanno Schlichting (hannosch) wrote | #1 |
| Changed in collective.buildout: | |
| status: | New → Opinion |
To post a comment you must log in.
If you want a hand-crafted zope.conf, use the zope-conf option of the p.r.zope2instance recipe and point to a location outside parts or if possible do them via the zope-conf-
If you depend on extensions, better put them inside a product and keep them out of the instance home. Any package using the "Products" namespace can contain an extensions folder, see for example https:/
It's part of buildouts design to wipe anything in the parts folder at pretty much any moment. Anything that's inside parts needs to be recreated by the responsible recipe on each run. For zope.conf there's two options that cover this already. Extensions are such an outdated concept, that I wouldn't want to do anything to encourage their use or document them any further.