Roel Bruggink wrote: > What are the options for including .mo files in an egg using > jarn.mkrelease or zest.releaser? > Vincent Fretin 'forbids' us including .mo files in svn[1], so they must > be generated after creating the tag.
You mean in addition to the two options mentioned at the link you refer to above (a MANIFEST file or using collective.releaser)? What's wrong with those recommendations? If you want to use the 'build_mo' command provided by collective.releaser from zest.releaser you could consider triggering this via the 'pre-release' hook (but I have not tried that myself though). > > The problem in not shipping .mo files lies in using a buildout cache and > running the instance as a user that doesn't have write permissions on > the cache, as davisagli told me on irc. > > Also, if I want to add the .mo files to the TinyMCE egg, should that > could as a new version, or just fixing a 'broken' egg? I'd say new release. Changing existing releases is generally considered a big no-no, as it can cause all sorts of trouble later on. Raphael > > [1] > http://vincentfretin.ecreall.com/articles/please-dont-put-.mo-files-in-subversion > -- > Roel Bruggink > http://www.fourdigits.nl/mensen/roel-bruggink > > Four Digits BV > http://www.fourdigits.nl > Willemsplein 44, 6811 KD, Arnhem > tel: +31(0)26 4422700 fax: +31(0)26 7600012 > KVK 091621370000 BTW 8161.22.234.B01 > > > ------------------------------------------------------------------------ > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
