bashareteam team mailing list archive

[Jeroen Vermeulen <jtv@xxxxxxxxxxxxx>]

Emilien Klein wrote:
> Hi Jeroen,

Hello!


> My name is Emilien Klein, and I am currently helping Guido Iodice with
> his project BaShare.
> He submitted a translation template a few weeks ago, but you didn't
> approve the upload because the template was named
> "BaShare/.lang/.pot". In order to get our translations in Launchpad, I
> had created a hard link called bashare.pot that linked to
> BaShare/.lang/.pot. The idea was to have a hard link "bashare.pot" ->
> "BaShare/.lang/.pot", so that when the original template got modified
> (the .pot file), the hard link would also get updated, and launchpad
> would detect the changes and update the translation template.
> However, the hard link is not working, once you get it in bzr it
> behaves as a completely different file, so we have to manually copy
> the .pot to the bashare.pot file and commit both files. This, as you
> can imagine, is not a satisfactory automatic behavior, and an
> unnecessary duplication of resources.

Using hard links for this sort of thing is a scary thing to do.  How it 
will behave depends very much on details of the platform and the tools 
that operate on it.  Unfortunately I suspect a softlink won't work 
either for this.


> I realize that the easy solution might seem to just rename the
> template ".pot" to something more suitable. However, this name is
> automatically chosen by our IDE Gambas:
>
> BaShare is written using Gambas. Gambas automatically creates the
> translation template, and stores it by automatically in a file called
> ".pot" in a project subfolder called ".lang". This explains why our
> translation template is located in the versioned file
> "BaShare/.lang/.pot".

That seems a pretty unusual choice!  Most operating systems will hide a 
file or directory with a name like that from view by default.

Is there no configuration item in Gambas to set a name, or to "export" 
the template to a more permanent location?


> Hard linking to this file is not a valid option in Bazaar, so I would
> like to ask if it is possible to import the original template file
> directly into the template "bashare" in BaShare trunk.

Okay; I've updated the path we have registered for the existing imported 
template, so that these uploads should go in automatically.  I can't say 
whether this will always work, so it'd still be nice to have some other 
solution if possible.  But for now I hope this lets you get on with things.


Jeroen