Teach dh_translations how to deal with meson
Bug #1751820 reported by
Gunnar Hjalmarsson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pkgbinarymangler (Ubuntu) |
Fix Released
|
Medium
|
Iain Lane |
Bug Description
dh_translations is currently not capable to find the gettext domain and generate the translation template on packages which use the meson build system. It would be convenient if it was.
I started to think about code changes, but got stuck:
I suppose that we'd better use ninja instead of intltool-update for such packages, and if so, we need to pass the build directory to the ninja() call. How would we do that?
Or would we use intltool-update also for such packages?
summary: |
- Learn dh_translations how to deal with meson + Teach dh_translations how to deal with meson |
Changed in pkgbinarymangler (Ubuntu): | |
assignee: | Gunnar Hjalmarsson (gunnarhj) → Iain Lane (laney) |
tags: | added: patch |
To post a comment you must log in.
That's a bit tricky. it looks like there is no easy way to "grep" for the domain under meson project. Some GNOME translators suggested that we might be able to get the value using "meson introspect" in the builddir.
If we don't figure out a reliable way to do that for meson projects then maybe we should add some extra arguments to dh_translations like --domain=<string> that let us provide the domain value from the debian/rules, that way we could keep using dh_translations rather than having to do custom override. We might also need a --refresh- target= <string> which would let us specifiy "make $domain- pot-update" , or maybe just detect meson build system and use "$domain- pot-update" for those