bqi: allow import of data in "update" mode

We used to support only 'init' or 'test' mode imports.
save_back: new util to save records from db back to XML files

This will hopefully help the developer load XML data from __openerp__
files, modify them on a live DB, and then save them *back* into the
module data files.
save_back: files shall have utf-8 content, when written to
save_back: "touch" option that updates ir.model.data from last save

If we want to use 'save_back' incrementally on our devel. db, we may
only want to save-back the changes we have done since last save.

"Touch" the ir.model.data with timestamp of last save, then only save
changes since that.
save_back: support for type="xml" content, for ui views

It is a common practice that view XML is contained as is, not escaped,
in the <record><field name="arch"> elements. The loader accepts the
type="xml" attribute in order to use that subtree.

We do the inverse here: store the arch as unescaped XML.
save_back: save 'ref' references back with their ir.model.data ID

Mainly in many2one fields, we use the 'ref' feature to connect one
record with another. Save back must reverse-resolve that into that
XML-id reference.
save-back: put new values into "eval"-ed fields

Fields like integers, floats, booleans etc. are often eval'ed in XML
to get their value. The inverse operation is repr() of a static val.
save_back: process CSV files, save ir.model.data ACL ones
save_back: better XML processing wrt. whitespace

whitespace around an embedded XML block (in an "arch" attribute) is
strip()ped on load, so we have to re-create it. Otherwise we would
introduce a diff each time we save_back.
save_back: allow text content to match an integer

There is some numeric fields, whose value was written in the XML text
content, like:
    <field name="sequence">10</field>

Don't change those, as long as the value is the same.
save_back: move into bin/ folder
save_back: ignore empty CSV lines
all: move, install "modulize" in home directory

"f3-modulize" is the utility that will generate RPM spec files from
OpenERP/F3 module definitions. It shall be accessible from any directory.
modulize: raise exceptions when version cannot be found
templates: rename "mageia.tmpl.spec" to common

We are going to share a common base
modulize: use a "default.spec", which extends the platform one

These two levels of redirection will allow customizing the result.
common.tmpl: whitespace, don't remove empty list
common.tmpl: use only manual provides/requires resolution for addons

Allowing rpmbuild to peek into every each file for requires/provides has
been slowing our process ever since 2008. We do know all dependencies
from the 'modulize' script, so we can prepare it in the spec file well
before `rpmbuild`.

This speeds package generation by an order of magnitude.
doc: start writing down where our files will be
spec: a spec file for gitbuild on Mageia

It is a simple copy of files in their right places