[Kde-extra-gear] Re: Message freeze for KimDaBa

[Jesper K. Pedersen]

Klas Kalass <klas.kalass at gmx.de> writes:

| Am Freitag, 30. Januar 2004 10:08 schrieb Jeroen Wijnhout:
| > On Friday 30 January 2004 09:16, Jesper K. Pedersen wrote:
| > > | It would be nice to know how translations in kdeextragear end up
| > > | getting distributed. I stopped translating kdenonbeta because it became
| > > | fairly clear they ended up in /dev/null or something like that. I know
| > > | how koffice and the regular modules get distributed, and I thought the
| > > | programs in kdeextragear were distributed with all translations, but
| > > | after the discussion on this list that is obviously not the case. So do
| > > | they get distributed in any way?
| > >
| > > I can obviously not speak for all programs in kdeextragear, as each of
| > > them are shipped separately, but I if there should be a kdeextragear
| > > project reading this and disagree, please speak up.
| > >
| > > KimDaBa uses cvs2dist to make packages. cvs2dist checks out both kind of
| > > translations, ie. .po and .docbooks files, and put those into the .tar.gz
| > > files. So yes, the translation are indeed uses.
| > >
| > > In addition I can also confirm that the RPM packages made out of the
| > > tar.gz files also do include the translations.
| >
| > This is how I used to do it as well. However there are some drawbacks:
| > cvs2dist stopped working for me (don't know why), the packages get huge if
| > you included many translations (so it is better to make a separate i18n
| > package), cvs2dist cannot deal with branches (leading to all sorts of
| > problems).
| 
| We have kdeextragear-1/scripts/cvsExtract.sh, which is intended to be "the" 
| packaging script for the extra gear. If there are any problems with that one, 
| please send a mail to this list. Sebastian Trueg seems to maintain it at the 
| moment :-)
I didn't know about that one.

How does it differ from cvs2dist?