On 11/1/07, Rafael Enrique Ortiz Guerrero <[EMAIL PROTECTED]> wrote: > > > On 10/31/07, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > > On 10/31/07, Sayamindu Dasgupta <[EMAIL PROTECTED]> wrote: > > > ** Current Status ** > > > > > > Most of the scripts, etc are ready, and we are quite satisfied with the > > > results of what we have seen so far using local repositories. The only > > > major "blocker" issue that is left to be resolved is the question of GIT > > > access to dev.laptop.org for the Pootle user. The most optimal solution > > > for this is to use the newly released support for GIT submodules (where > > > the po directory can be a separate submodule of a project). This > > > isolates the PO directory from the rest of the project, minimising the > > > chances of Pootle messing something other than translations :-). > > > > > > However, we would like to hear from developers on this - does having a > > > new submodule under your project tree complicate your job ? Information > > > on git submodules and how to use them is available at > > > http://git.or.cz/gitwiki/GitSubmoduleTutorial > > From my point of view this is not really necessary, we can keep on doing our > actual simlinks and script scheme, although is not an entirely integration > to git (from the pootle point of view), from the d.l.o side is the better > solution, but anyway im not saying that we shouldn't keep on trying to find > a complete solution for this, but this solution does not have to be so > complex. > > So i agree with marco that we have to write a tutorial about this, but the > procedure is not difficult, taking in count that we have to handle the > translation sync from the translate machine, and this is made by git pull > from all the activities.
Yeah, my request for a "tutorial" was about the submodule part. It felt too complex at first sight but I wanted to see exactly what we was going to require for activity authors. Anyway if we can avoid the step altogether I'll be happy :) Marco _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
