Re: [PATCH v2 08/20] po: detect zanata binary during configure time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 24, 2019 at 01:50:50PM +0200, Pavel Hrdina wrote:
> Currently we had hard-coded `zanata` as a name of the binary, but
> it can also be `zanata-cli`.

FWIW, I hardcoded 'zanata' for two reasons

 - It is a light weight python client, compared to the java
   client which pulls in a huge dep chains.
 - I found the java client unreliable eg several times when
   pushing a new .pot file, it pushed the pot but failed to tell
   the server to preserve existing translations, so we lost all
   translations.

I'd hope the latter is fixed now, but honestly I would still
not recommend using the java client, when the python client
is working nicely.

Is there a particular reason you wanted to make it autodetect ?

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 :|

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list





[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux