all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 7/7] network-interface-pinning: generate proper manpage from docs
Date: Tue, 23 Jun 2026 11:43:24 +0200	[thread overview]
Message-ID: <20260623094419.330174-8-c.heiss@proxmox.com> (raw)
In-Reply-To: <20260623094419.330174-1-c.heiss@proxmox.com>

Now that pve-docs has a dedicated man page set up for
pve-network-interface-pinning, let the build process generate it from
there.

Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Requires a bumped pve-doc-generator with

  pve-doc-generator: handle CLI tools/services with dashes in their name

applied, so that pve-doc-generator correctly import the CLI module.

 bin/Makefile | 19 -------------------
 1 file changed, 19 deletions(-)

diff --git a/bin/Makefile b/bin/Makefile
index 5d225d179..d04e4fefa 100644
--- a/bin/Makefile
+++ b/bin/Makefile
@@ -69,25 +69,6 @@ all: $(SERVICE_MANS) $(CLI_MANS)
 	podselect $* > $@.tmp
 	mv $@.tmp $@
 
-pve-network-interface-pinning.1:
-	printf "pve-network-interface-pinning" > $@.tmp
-	printf ".TH PVE-NETWORK-INTERFACE-PINNING 1\n.SH NAME\npve-network-interface-pinning \- Assisted interface name pinning.\n" > $@.tmp
-	printf ".SH DESCRIPTION\nThis tool helps you to configure a network interface name pinning \
-	 and adapting all relevant Proxmox VE config files.\n" >> $@.tmp
-	mv $@.tmp $@
-
-pve-network-interface-pinning.api-verified:
-	perl ${PERL_DOC_INC} -T -e "use PVE::CLI::pve_network_interface_pinning; PVE::CLI::pve_network_interface_pinning->verify_api();"
-	touch 'pve-network-interface-pinning.service-api-verified'
-
-pve-network-interface-pinning.zsh-completion:
-	perl ${PERL_DOC_INC} -T -e "use PVE::CLI::pve_network_interface_pinning; PVE::CLI::pve_network_interface_pinning->generate_zsh_completions();" >$@.tmp
-	mv $@.tmp $@
-
-pve-network-interface-pinning.bash-completion:
-	perl ${PERL_DOC_INC} -T -e "use PVE::CLI::pve_network_interface_pinning; PVE::CLI::pve_network_interface_pinning->generate_bash_completions();" >$@.tmp
-	mv $@.tmp $@
-
 pve8to9.1:
 	printf ".TH PVE8TO9 1\n.SH NAME\npve8to9 \- Proxmox VE upgrade checker script for 8.4+ to current 9.x\n" > $@.tmp
 	printf ".SH DESCRIPTION\nThis tool will help you to detect common pitfalls and misconfguration\
-- 
2.54.0





      parent reply	other threads:[~2026-06-23  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  9:43 [PATCH docs/manager 0/7] interface-pinning: add rename subcommand and man(1) page Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 1/7] network: fix typo occurences -> occurrences Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 2/7] pve-doc-generator: handle CLI tools/services with dashes in their name Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 3/7] pve-network-interface-pinning: init man(1) page Christoph Heiss
2026-06-23  9:43 ` [PATCH docs 4/7] network: pinning: mention how to rename an interface Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 5/7] network-interface-pinning: avoid warning if `bond-primary` is unset Christoph Heiss
2026-06-23  9:43 ` [PATCH manager 6/7] network-interface-pinning: add method for renaming existing pins Christoph Heiss
2026-06-23  9:43 ` Christoph Heiss [this message]

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=20260623094419.330174-8-c.heiss@proxmox.com \
    --to=c.heiss@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