GMO files?

[Richard Heck]

I am all but ready to release 2.1.2. But I noticed that Kornel committed
a GMO file after fixing up something to do with pl.po. Is there
something I need to do to regenerate and then commit GMO files?

Richard

[Jean-Marc Lasgouttes]

Post by Richard Heck
I am all but ready to release 2.1.2. But I noticed that Kornel committed
a GMO file after fixing up something to do with pl.po. Is there
something I need to do to regenerate and then commit GMO files?

Try "make update-gmo" in po directory. But maybe "make dist" does that?

JMarc

[Kornel Benko]

Post by Richard Heck
I am all but ready to release 2.1.2. But I noticed that Kornel committed
a GMO file after fixing up something to do with pl.po. Is there
something I need to do to regenerate and then commit GMO files?
Richard

Using automake, it suffices to call 'make dist'. The po- and gmo-files are automatically recreated.
Using cmake one calls 'make update-po'.

What I did, was 'make update-gmo', which updates only the gmo-file of a newly edited po-file (cmake).

Kornel

[Richard Heck]

Post by Kornel Benko

Post by Richard Heck
I am all but ready to release 2.1.2. But I noticed that Kornel committed
a GMO file after fixing up something to do with pl.po. Is there
something I need to do to regenerate and then commit GMO files?
Richard

Using automake, it suffices to call 'make dist'. The po- and gmo-files are automatically recreated.
Using cmake one calls 'make update-po'.
What I did, was 'make update-gmo', which updates only the gmo-file of a newly edited po-file (cmake).
Try "make update-gmo" in po directory. But maybe "make dist" does that?

OK, I did update-gmo. I guess this should be done every time a new po
file is committed?

What exactly does "make dist" do? I see it produced a tar.gz and tar.bz2
file.

Richard

[Kornel Benko]

Post by Richard Heck

Post by Kornel Benko

Post by Richard Heck
I am all but ready to release 2.1.2. But I noticed that Kornel committed
a GMO file after fixing up something to do with pl.po. Is there
something I need to do to regenerate and then commit GMO files?
Richard

Using automake, it suffices to call 'make dist'. The po- and gmo-files are automatically recreated.
Using cmake one calls 'make update-po'.
What I did, was 'make update-gmo', which updates only the gmo-file of a newly edited po-file (cmake).
Try "make update-gmo" in po directory. But maybe "make dist" does that?

OK, I did update-gmo. I guess this should be done every time a new po
file is committed?
What exactly does "make dist" do? I see it produced a tar.gz and tar.bz2
file.

To my understanding it should create a distributable source package.
You should be able to use 'configure; make' on it (autoconf),
and also 'cmake;make'. But the later is only for lyx2.2 realised.

Post by Richard Heck
Richard

Kornel

[Pavel Sanda]

OK, I did update-gmo. I guess this should be done every time a new po file
is committed?

I think that doing it once upon a time (like when doing release) is enough.
Except for translators who might want it for testing and who know how to do it
in their local tree the only gain is that you produce more commit garbage and
size of the git archive.

What exactly does "make dist" do? I see it produced a tar.gz and tar.bz2
file.

Prepares all files needed (e.g. remerge translation IIRC) for distribution
and make tarballs. I believe you use it every release or no?

Pavel

[Jürgen Spitzmüller]

Post by Pavel Sanda
I think that doing it once upon a time (like when doing release) is enough.
Except for translators who might want it for testing and who know how to do it
in their local tree the only gain is that you produce more commit garbage and
size of the git archive.

The reason why it is done more often recently, I suppose, is that we now
track gmo files via git (which was not done before). I also usually commit
de.gmo changes, just for the sake of my git status.

But in general, I agree that it should suffice to do it every once in a
while.

JÃŒrgen