On 2012-10-13 23:44:31 +0000, Maurits van Rees said:
[Sorry, I had incorrecty sent this only to Alex Clark.]
And I thought, "that's odd" but answered privately anyway :-)
Op 13-10-12 15:39, Alex Clark schreef: > So, if it's true that "plonetest" is > intended to be used as "buildouts for plone" (not just "testing > add-ons") then it really should be called "buildout.plone" IMHO. Or, if > it really is just for "testing add-ons" then maybe it shouldn't be > renamed. Again, *SHRUG* Its one and only purpose is to test add-ons. Example: I have this buildout.cfg in the root of the collective.catalogcleanup package: [buildout] extends = http://svn.plone.org/svn/collective/buildout/plonetest/test-4.x.cfg package-name = collective.catalogcleanup test-eggs = collective.catalogcleanup[test] These are just four lines. Okay, I have removed a few lines for clarity, as I like to make my argument stronger. With these four lines I get a proper bin/instance and bin/test fit for my package. And less important here, but more with Plone 3 testing: you get properly pinned versions for zc.recipe.testrunner and zope.testing instead of getting too new versions that do not work in Plone 3. Try it. You will like it. I don't care what name this has on github, as long as 'plonetest' is in it: that is what the current users expect and it is what they will search for on github.com if they wonder if this is on github already or not.
Done: https://github.com/collective/buildout.plonetest
Cheers,
-- Alex Clark ยท https://www.gittip.com/aclark4life/ _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
