[bt-devel] rpm questions

Fred Saalbach bt-devel@crosswire.org
Thu, 30 May 2002 21:35:35 -0400


:-)
Martin Gruner wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> > I have no objection to putting the english back in the main tree.
> > Marten, it might be best if you moved it so that it goes in the correct
> > place.  Or if you want me to do it, Let me know where to put the docs.
> 
> Ok. I'll wait for Joachim to agree and then I can do the cvs reorganisation.
> 
> > Could we create a branch of the cvs tree for translations, then
> > structure it in a way that best suites the translators?  Perhaps a
> > branch for each active language, and a sub branch for the release being
> > worked on currently and another for the previous release translation
> > which can be useful for kbabel translation directories.
> 
> Not sure if I understand what exactly you mean. I propose that each language
> gets its own cvs directory, like
> 
> bibletime-i18n-de
> bibletime-i18n-fr
> etc.
> 
> Within these cvs modules you can have version trees which would do what you
> are referring to, am I right here? You might want to look at the info page of
> cvs to see how exactly this works (I don't really know either, Joachim
> manages this). Basically you set tags when a version is relased, like rel-1-2
> for the latest release we had. Then you can create a branch in cvs. For an
> example, open cervisia, select main.cpp, then menu View->browse
> Log->Treeview, you can see the branches there well.

That is exactly what I intended.  I must not have explained myself
clearly.
> 
> > Might also be useful if the translators can work directly in their CVS.
> 
>  Yes, I think so, but I'd assume that they won't really like it. Atm Joachim
> sends them the files that are to be translated and they'll give him the
> results.

Either method will work fine.  They should be aware that they can work
directly with the CVS, or send in a package as is the current practice.

Fred Saalbach

> 
> Martin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE89J8jwyLo8U2VzYcRAsfCAJ4wTicnN5ejQs3BiHRAMwU7Yb63SgCbBFW8
> iit4NTCUIB1aVfyqITvKPW4=
> =WiVz
> -----END PGP SIGNATURE-----