Changes in v4:
* rather than searching for wide characters, tell parse_config()
  directly whether the file was registered as UTF-8

Changes in v3:
* rebase on current master.
* add patch to use strict UTF-8 encoding when writing.
* use strict UTF-8 for {de,en}coding in the rest of the series.
* let cfs_register_file() take an $options parameter rather than
  an $utf8 parameter, so future call sites are more readable.

Changes in v2:
* rebase on current master.
* use qw(encode) when importing Encode module.

A configuration file registered as UTF-8 will be automatically decoded
from UTF-8 to Perl's internal string format after reading and encoded
in the other direction before writing.

Patch 1/5 also makes sense without the rest of the RFC.

Note that patch 4/5 (required by 3/5) is a versioned breaks for
libpve-access-control which still needs to be bumped! Could be avoided
by keeping the implicit return of cfs_register_file(), but that's bad
for encapsulation.

Versioned dependency bump pve-cluster -> pve-common needed!

common:

Fiona Ebner (2):
  file: set contents: use strict UTF-8 encoding with $force_utf8
  section config: prepare for supporting UTF-8 encoded configurations

 src/PVE/File.pm          |  2 +-
 src/PVE/SectionConfig.pm | 29 ++++++++++++++++++++++++-----
 2 files changed, 25 insertions(+), 6 deletions(-)


cluster:

Fiona Ebner (3):
  cfs register file: avoid implicit return
  d/control: add versioned breaks for libpve-access-control
  cluster files: support registering UTF-8 configuration file

 debian/control     |  2 +-
 src/PVE/Cluster.pm | 20 ++++++++++++++++----
 2 files changed, 17 insertions(+), 5 deletions(-)


Summary over all repositories:
  4 files changed, 42 insertions(+), 11 deletions(-)

-- 
Generated by git-murpp 0.5.0



Reply via email to