search

plone / papyrus

A buildout to run multiple versions of the plone documentation
GNU General Public License v2.0
8 stars 7 forks source link

Make buildout.cfg more modular #12

Closed svx closed 10 years ago

svx commented 10 years ago

At the moment, we have everything in one long buildout.cfg from the base setup, over transiflex to our robots, this makes the buildout.cfg becoming harder to maintain and also often I do not need/want everything [read testing for example]. Would it an idea to move all the different parts into their own config dirs and just include them into the main buildout.cfg . example: config/versions config/transiflex config/robots

this would make the main buildout.cfg much shorter and better to read

svx commented 10 years ago

I started to work on that: https://github.com/plone/papyrus/tree/wip-new-structure this is pretty much WIP but imho this is much more readable :) opinions ? :)

svx commented 10 years ago

Well the whole ideas was to split the main buildout in smaller parts, to make it easier to maintain, and also have something like a 'debug.cfg' because most of the time we do not need a full build with the whole Plone stack and robot-framework, but to have a decent setup this turns out to be a bit painful, because of the way how sphinx works and how we did out setup.

I guess for have something like a 'debug setup' its is easier to use a own branch. It is not that easy to use different .conf files assigned to different Makefiles, sadly, sadly we never thought about that from the beginning, question here does it make sense to continue with the splitting of the buildout ?

after some thinking a 'debug' branch will not sole that problem at all, since it would still relies on the .conf for the docs repo, any other ideas ? @polyester @datakurre @giacomos what do you think ?
svx commented 10 years ago

I close that issue and will delete the branch, with the new setting in our Makefile 'debug-eng' this is good enoughm if we have later more languages we can easily add them.