Grok should include Zope3 version.cfg instead of merging it
Bug #357550 reported by
Sylvain Viollon
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grok |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
It will be interesting to extend the version.cfg of Zope3 in the Grok version.cfg, where we could add new version for some packages or change others. The advantage are:
- It's easy to always use the lastest version (we don't need a clever script or spend time to merge or check results),
- So it's less error prone on merge,
- We can clearly see which package are not included in Zope3, and for which package we don't use the same version that Zope 3,
The disadvantages are:
- We have one more file :).
Revision history for this message
| Sylvain Viollon (thefunny) wrote | #1 |
| Changed in grok: | |
| importance: | Undecided → Low |
| milestone: | none → 1.1 |
| status: | New → Fix Committed |
| Changed in grok: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Well, I think it's done now since grok and grokcore components refer to the groktoolkit version.cfg with directly use version.cfg of the ZTK.