public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container] fix #7156: setup: separate dns list with semicolons
Date: Thu, 18 Dec 2025 15:09:21 +0100	[thread overview]
Message-ID: <66795e25-297c-4382-95a6-95ba687586b7@proxmox.com> (raw)
In-Reply-To: <s8o1pks19pj.fsf@proxmox.com>

On 18/12/2025 09:21, Maximiliano Sandoval wrote:
> Yes, but the quote is from the nm-settings man page. GLib's .ini format
> allows to decide which separator to use **globally**, see [2], it does
> not allow for some lists will be handled with one separator while others
> with another, not without out-of-tree parsing at least. There are some
> exceptions in nm-settings though, but they are mentioned in the man page
> and are not handled as lists, namely:
> 
> ```
> Also, some lists of complex values (addresses, routes, routing-rules),
> instead of using a semicolon separated list, use one key-value pair per
> list element,
> ```
> 
> [2] https://docs.gtk.org/glib/method.KeyFile.set_list_separator.html

Oof... But in this should IMO then get added to the commit message, as
when I check the docs and see examples with either variant, but without
having mentioned that it depends which variant is OK when, then any
rationale in the commit messages helps me a ton to figure that out for
myself quickly.

Do you mind re-sending this with the commit message amended? Maybe we can
also introduce a local glib_join_list helper that is basically just a
wrapper like sub { return join(';', @_); } with a comment above?
We have quite some distros we support here and things do change but in
varying rates, so such semantic helpers can be quite nice to have.

Adding already a test case would be also appreciated, hopefully the
"src/test/test-centos10-001" one can be copied and adapted to cover
this case here.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-12-18 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 15:06 Maximiliano Sandoval
2025-12-17 21:31 ` Thomas Lamprecht
2025-12-17 21:36 ` Thomas Lamprecht
2025-12-18  8:21   ` Maximiliano Sandoval
2025-12-18 14:09     ` Thomas Lamprecht [this message]
2025-12-18 15:04       ` [pve-devel] superseded: " Maximiliano Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66795e25-297c-4382-95a6-95ba687586b7@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal