Re: [Qemu-devel] Last call for release-critical fixes for 2.12

["Daniel P. Berrangé" <berrange@redhat.com>]

On Tue, Apr 17, 2018 at 04:05:46PM +0200, Stefan Weil wrote:
> Am 17.04.2018 um 15:50 schrieb Peter Maydell:
> > On 17 April 2018 at 14:19, Stefan Weil <sw@weilnetz.de> wrote:
> >> Update po files? That's not a "must fix", but it would be nice to have
> >> those files synchronized with ui/gtk.c again.
> > Judging by the "POT-Creation-Date" timestamps, we haven't done
> > that for a year or so, so there doesn't seem to be a great
> > urgency to do it now.
> >
> > Overall:
> >  * I don't really understand why we need to keep doing this;
> >    I tried "make -C po update" but all it did was update the
> >    date stamp and a bunch of comments in the .po files
> >  * If we do need to do this, we need to come up with a
> >    process (preferably automatic) that ensures that we do
> >    it in a more timely manner than "somebody mentions it
> >    on the day we're thinking of tagging the final rc"
> >
> > Asking me to manually run a magic command I don't understand
> > doesn't really work, as you can see from how infrequently
> > it's happened.
> >
> > thanks
> > -- PMM
> 
> The only visible consequence if it is not done is that developers who
> run "make install" (which updates the po files) then have a local code
> modification which is in the way if they are working with git. Not many
> run "make install", and obviously those who do can handle the situation.
> I think that there would be a real problem if people tried to build with
> the source on a read only medium.
> 
> I wonder whether generating the po files without the line comments would
> improve the situation. Currently each added or removed line in ui/gtk.c
> changes the line numbers which are part of the comments. If the comments
> would not include line numbers, then only relevant changes of message
> texts would need an update of the po files. Maybe we should try that for
> the next release.

Yes, storing full po files in GIT is really awful for a number of reasons.
Stripping source location comments when storing in git is good, because
those because out of date the moment someone changes the code containging
the original msgid. You also want to sort msgids alphabetically instead
by source location so you don't get stuff moving around all in the po
file when code is refactored/moved/renamed.

I've coincidentally been tackling this same problem in libvirt just last
week

  https://www.redhat.com/archives/libvir-list/2018-April/msg01004.html

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|