From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Max Carrara <m.carrara@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 pve-common 01/12] introduce PVE::Path
Date: Fri, 31 Jan 2025 13:33:15 +0100 [thread overview]
Message-ID: <bfae248c-de2c-486c-a058-e274e2b48597@proxmox.com> (raw)
In-Reply-To: <b1d89b2a-4fdc-4e2b-84e4-1c91abb6dbb5@proxmox.com>
Am 31.01.25 um 13:23 schrieb Fiona Ebner:
> Am 09.01.25 um 15:48 schrieb Max Carrara:
>> +=head3 path_join(@paths)
>> +
>> +Joins multiple paths together. All kinds of paths are supported.
>> +
>> +Does not perform any C<L<< normalization|/"path_normalize($path)" >>>.
>> +
>> + my $joined = path_join("foo", "bar/baz", "qux.txt");
>> + # foo/bar/baz/qux.txt
>> +
>> + my $joined = path_join("/", "etc/pve/", "storage.cfg");
>> + # /etc/pve/storage.cfg
>> +
>> +Similar to C<L<< path_push()|/"path_push($path, $other)">>>, should any of the
>> +C<@paths> be an absolute path, it I<replaces> all preceding paths.
>
> Seems like the docs are somehow broken here, looking at it with perldoc,
> it just states 'Similar to "path_push()"' and the rest of the sentence
> is missing.
>
perldoc src/PVE/Path.pm will tell you at the end:
POD ERRORS
Hey! The above document had some coding errors, which are explained
below:
Around line 160:
Unknown directive: =items
Around line 209:
Unterminated C<L< ... >> sequence
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-01-31 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 14:48 [pve-devel] [PATCH v3 pve-common 00/12] Introduce and Package PVE::Path & PVE::Filesystem Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 01/12] introduce PVE::Path Max Carrara
2025-01-31 12:23 ` Fiona Ebner
2025-01-31 12:33 ` Fiona Ebner [this message]
2025-02-03 14:21 ` Max Carrara
2025-02-03 15:42 ` Fiona Ebner
2025-02-03 16:45 ` Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 02/12] test: add directory for tests of PVE::Path module Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 03/12] test: add tests for path_is_absolute and path_is_relative of PVE::Path Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 04/12] test: add tests for path_components " Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 05/12] test: add tests for path_join " Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 06/12] test: add tests for path_push " Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 07/12] test: add tests for path_parent " Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 08/12] test: add tests for path_starts_with, path_ends_with, path_equals Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 09/12] test: add tests for file path operation functions of PVE::Path Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 10/12] test: add tests for path_normalize " Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 11/12] introduce PVE::Filesystem Max Carrara
2025-01-31 12:44 ` Fiona Ebner
2025-02-03 14:21 ` Max Carrara
2025-01-09 14:48 ` [pve-devel] [PATCH v3 pve-common 12/12] debian: introduce package libproxmox-fs-path-utils-perl Max Carrara
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=bfae248c-de2c-486c-a058-e274e2b48597@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=m.carrara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal