From 61068fc6794df8f4e0ad2b33b6530f2b95bab79c Mon Sep 17 00:00:00 2001
From: iamashwin99 <ashwin-kumar.karnad@mpsd.mpg.de>
Date: Wed, 28 Jun 2023 13:51:09 +0200
Subject: [PATCH] set the command name in the examples without full path
---
src/mpsd_software_manager/mpsd_software.py | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/mpsd_software_manager/mpsd_software.py b/src/mpsd_software_manager/mpsd_software.py
index 0c17450..eed840a 100755
--- a/src/mpsd_software_manager/mpsd_software.py
+++ b/src/mpsd_software_manager/mpsd_software.py
@@ -27,6 +27,7 @@ except ModuleNotFoundError:
else:
rich_available = True
+command_name = Path(sys.argv[0]).name
about_intro = f"""
Build software as on MPSD HPC.
@@ -45,7 +46,7 @@ Build software as on MPSD HPC.
Command line usage:
- $> {sys.argv[0]}
+ $> {command_name}
"""
@@ -58,15 +59,15 @@ Examples:
1. Query what package sets and toolchains are available for installation in
release dev-23a
- $> {sys.argv[0]} available dev-23a
+ $> {command_name} available dev-23a
2. Install foss2022a-serial toolchain from the dev-23a release
- $> {sys.argv[0]} install dev-23a foss2022a-serial
+ $> {command_name} install dev-23a foss2022a-serial
3. Check what package sets and toolchains are installed from release dev-23a
- $> {sys.argv[0]} status dev-23a
+ $> {command_name} status dev-23a
The `status` command also displays the `module use` command needed to load
the created modules.
--
GitLab