[Zopeskel] [ZopeSkel Issue Tracker] #35 - Re: zopeskel plone3_buildout --svn-repository fails
A new response has been given to the issue **zopeskel plone3_buildout --svn-repository fails** in the tracker **Issue tracker** by **Cris Ewing**. Response Information Issue zopeskel plone3_buildout --svn-repository fails (http://plone.org/products/zopeskel/issues/35) Confirmed - In progress (UNASSIGNED) - cewing **Response Details**:: according to claytron: 'It is definitely paster assuming that the template will be an egg and not a buildout when checking the code in.' This jibes with what I've seen. Claytron also suggests: 'In my custom code, I just set the svn:ignore property for stuff like that in the post method.' I'm going to do that for this particular case and see if it helps. * This is an automated email, please do not reply - plone.org Administrator___ ZopeSkel mailing list ZopeSkel@lists.plone.org http://lists.plone.org/mailman/listinfo/zopeskel
[Zopeskel] [ZopeSkel Issue Tracker] #35 - Re: zopeskel plone3_buildout --svn-repository fails
A new response has been given to the issue **zopeskel plone3_buildout --svn-repository fails** in the tracker **Issue tracker** by **Cris Ewing**. Response Information Issue zopeskel plone3_buildout --svn-repository fails (http://plone.org/products/zopeskel/issues/35) In progress - Postponed cewing - (UNASSIGNED) **Response Details**:: Crud. Never mind. This particular problem cannot be solved in ZopeSkel. The issue is quite clearly in Paster, which assumes that everything it builds is an egg and will have an egg-info directory. Even setting svn-ignore will not solve this problem and so the only choice I think we have is to swallow the --svn- repository variable in all buildout templates. * This is an automated email, please do not reply - plone.org Administrator___ ZopeSkel mailing list ZopeSkel@lists.plone.org http://lists.plone.org/mailman/listinfo/zopeskel
[Zopeskel] [ZopeSkel Issue Tracker] #35 - Re: zopeskel plone3_buildout --svn-repository fails
A new response has been given to the issue **zopeskel plone3_buildout --svn-repository fails** in the tracker **Issue tracker** by **Roel Bruggink**. Response Information Issue zopeskel plone3_buildout --svn-repository fails (http://plone.org/products/zopeskel/issues/35) **Response Details**:: Not supporting --svn-repository seems like a sensible solution to me. A workaround is to run ZopeSkel on a working copy. example: cd src svn co repos my.package ZopeSkel create -t type my.package * This is an automated email, please do not reply - plone.org Administrator___ ZopeSkel mailing list ZopeSkel@lists.plone.org http://lists.plone.org/mailman/listinfo/zopeskel
