de3289e2b5
There was one attempt a year ago done by me to drop HAL [1] but it was never resolved. There was another time when Dan suggested to drop HAL driver [2] but it was decided to keep it around in case device assignment will be implemented for FreeBSD and the fact that virt-manager uses node device driver [3]. I checked git history and code and it doesn't look like bhyve supports device assignment so from that POV it should not block removing HAL. The argument about virt-manager is not strong as well because libvirt installed from FreeBSD packages doesn't have HAL support so it will not affect these users as well [4]. The only users affected by this change would be the ones compiling libvirt from GIT on FreeBSD. I looked into alternatives and there is libudev-devd package on FreeBSD but unfortunately it doesn't work as it doesn't list any devices when used with libvirt. It provides libudev APIs using devd. I also looked into devd directly and it provides some APIs but there are no APIs for device monitoring and events so that would have to be somehow done by libvirt. Main motivation for dropping HAL support is to replace libdbus with GLib dbus implementation and it cannot be done with HAL driver present in libvirt because HAL APIs heavily depends on symbols provided by libdbus. [1] <https://www.redhat.com/archives/libvir-list/2019-May/msg00203.html> [2] <https://www.redhat.com/archives/libvir-list/2016-April/msg00992.html> [3] <https://www.redhat.com/archives/libvir-list/2016-April/msg00994.html> [4] <https://svnweb.freebsd.org/ports/head/devel/libvirt/Makefile?view=markup> Signed-off-by: Pavel Hrdina <phrdina@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> |
||
|---|---|---|
| .. | ||
| as.po | ||
| bg.po | ||
| bn_IN.po | ||
| bs.po | ||
| ca.po | ||
| cs.po | ||
| da.po | ||
| de.po | ||
| el.po | ||
| en_GB.po | ||
| es.po | ||
| fi.po | ||
| fr.po | ||
| gu.po | ||
| hi.po | ||
| hu.po | ||
| id.po | ||
| it.po | ||
| ja.po | ||
| kn.po | ||
| ko.po | ||
| libvirt.pot | ||
| LINGUAS | ||
| meson.build | ||
| mk.po | ||
| ml.po | ||
| mr.po | ||
| ms.po | ||
| nb.po | ||
| nl.po | ||
| or.po | ||
| pa.po | ||
| pl.po | ||
| POTFILES.in | ||
| pt_BR.po | ||
| pt.po | ||
| README.rst | ||
| ru.po | ||
| sr.po | ||
| sr@latin.po | ||
| sv.po | ||
| ta.po | ||
| te.po | ||
| uk.po | ||
| vi.po | ||
| zh_CN.po | ||
| zh_TW.po | ||
Libvirt Message Translation
Libvirt translatable messages are maintained using the GNU Gettext tools and file formats, in combination with the Fedora Weblate web service.
https://translate.fedoraproject.org/projects/libvirt/libvirt/
Source repository
The libvirt GIT repository stores the master "libvirt.pot" file, which is to be refreshed at time of feature freeze.
The "po" files stored in GIT have source locations removed in order to cut down on storage size, by eliminating information already present in the "pot" file. All files are stored with strings sorted in alphabetical order rather than source location order, to minimize movement of strings when source locations change.
The "po" files are to be EXCLUSIVELY UPDATED by merge requests sent from the Fedora Weblate service. Other contributors MUST NEVER send changes which touch the "po" file content, as that will create merge conflicts for Weblate. IOW any bug fixes to translations should be made via the Weblate application UI.
After the "pot" file in libvirt GIT, Weblate will automatically run "msgmerge" to update the "po" files itself and send back a merge request with the changes.
Translation updates made in the Weblate Web UI will be committed to its fork of the GIT repo once a day. These commits will be submitted back to the master GIT repo via merge requests. If a merge request from Weblate is already open, commits will be added to this existing merge request. Weblate will take care of rebasing whenever changes happen in Git master. In order to avoid having to do translations merges 30 times a month, merge requests from Weblate will usually be left open until feature freeze arrives. During the freeze period, they will be accepted more promptly to ensure they make it into the new release.