Auto-generate POT files when importing from bazaar branches

Registered by Данило Шеган

Since POT files are usually not kept inside source code branches, but are instead regenerated on build time, we should re-generating them when trying imports from branches. We should support at least intltool and GNU gettext set-ups with Makevars/POTFILES[.in] files. Easy way to support regeneration is to allow linking of branches and soyuz, letting soyuz build templates for us (which would work for all cases).

There are a lot of security implications (intltool and xgettext have not been audited, so we'd likely have to run them in a chroot), and some performance concerns (we need a full checkout to be able to rebuild POT files, and we can't do it in-memory like we do for static POT imports), making this a complex job. See https://dev.launchpad.net/Soyuz/Specs/BuilddGeneralisation

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Jeroen T. Vermeulen
Completed by
Curtis Hovey

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.