Re: Re: dist_plone script in cvs

On Thu, 18 Mar 2004 15:40:02 +0100, Simon Eisenmann  
<simon-4x/[email protected]> wrote:

> Right now the dist_plone script uses the PloneBase tarball from sf,
> which doesnt contain the i18n folder. Imho this is correct.

Yup. I also want the i18n part scripted, as it is forgotten very often  
when we create a tarball. ;)

> The i18nteam needs to make releases themselves which clarify the
> translations for plone version x. So far the dist_plone script isnt able
> to include the i18n files since there is no release of them.
>
> I suggest to make them a seperate product aka PloneTranslations which
> includes a single __init__.py and the i18n folder, so we dont have to
> mix CMFPlone and the translations together.

Sounds good. CC-ing the i18n list.

Later on, SVN can save us, of course - but for now this would be the best  
approach.

Jodok/Godefroid/Daniel - do you have the time to do this anytime soon?  
We're trying to make it a rule that Plone is always built from released  
tarballs, and i18n should be no exception. This eases troubleshooting, and  
allows us to have somewhat intelligent build scripts (which is what Simon  
has built for us now :).

-- 
__________________________________________________________________

  Alexander Limi   ·   Interaction Architect   ·   Plone Solutions

  Development · Training · Support · http://www.plonesolutions.com
__________________________________________________________________

  Plone Co-Founder   ·   http://plone.org   ·   Connecting Content



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click