Geek asks and answers

How to set up to develop flat products

I want to develop several products for a specific installation / version of Plone, which I cannot change (3.3.5).

What is the best way to organize the source tree, so that I don’t need to insert a huge instance of plone into the original control, which will not change? I still want to use buildout for local validation though ...

What do you recommend?

I am on Windows and prefer git hg, but I can live with both ...

+3
source share
3 answers

In general, this is being done now-in-a-day with mr.developer. You can use this build method:

[buildout]
extends = 
    https://raw.githubusercontent.com/plock/pins/master/plone-4-3
    https://raw.githubusercontent.com/plock/pins/master/dev

Then add the sources to the parameter auto-checkoutin the section [buildout]and in the section [sources]in the format described here:

- :

[buildout]
auto-checkout = my.package

[sources]
my.package = git https://url.to/my.package

eggs plone.recipe.zope2instance, :

[instance]
recipe = plone.recipe.zope2instance
eggs =
    Pillow
    Plone
    my.package

. Plone coredev buildout :

, develop [buildout], " " ( ):

[buildout]
develop = src/my.package
+10

Just create the buildout.cfg file in the root directory of your egg / product and expand the plonetest buildout from the collective:

[buildout]
extends =
    http://svn.plone.org/svn/collective/buildout/plonetest/plone-3.3.x.cfg

package-name = collective.mypackage

Thus, you will need to add only two files (buildout.cfg and bootstrap.py) to your repository.

For a complete example, see http://svn.plone.org/svn/plone/plone.app.discussion/trunk/ .

If you are developing more than one package, perhaps mr.developer is probably the way to go.

+1
source

More articles:


All Articles