From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: corbet@lwn.net, rppt@linux.ibm.com, rfontana@redhat.com,
kstewart@linuxfoundation.org, bhelgaas@google.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/sphinx-pre-install: add how to exit virtualenv usage message
Date: Wed, 18 Sep 2019 06:29:21 -0300 [thread overview]
Message-ID: <20190918062921.73a45f2d@coco.lan> (raw)
In-Reply-To: <20190917224805.2762-1-skhan@linuxfoundation.org>
Hi Shuah,
Em Tue, 17 Sep 2019 16:48:05 -0600
Shuah Khan <skhan@linuxfoundation.org> escreveu:
> Add usage message on how to exit the virtualenv after documentation
> work is done.
Good idea.
>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
> scripts/sphinx-pre-install | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/scripts/sphinx-pre-install b/scripts/sphinx-pre-install
> index 3b638c0e1a4f..932547791e3c 100755
> --- a/scripts/sphinx-pre-install
> +++ b/scripts/sphinx-pre-install
> @@ -645,6 +645,12 @@ sub check_distros()
> # Common dependencies
> #
>
> +sub deactivate_help()
> +{
> + printf "\tWhen work is done exit the virtualenv:\n";
> + printf "\tdeactivate\n";
I would change the message to something like:
If you want to exit the virtualenv, you can use:
deactivate
Btw, at least here, I recently noticed a conflict between the
virtenv and scripts/spdxcheck.py. Running deactivate solves it.
Regards,
Mauro
> +}
> +
> sub check_needs()
> {
> # Check for needed programs/tools
> @@ -686,6 +692,7 @@ sub check_needs()
> if ($need_sphinx && scalar @activates > 0 && $activates[0] ge $min_activate) {
> printf "\nNeed to activate a compatible Sphinx version on virtualenv with:\n";
> printf "\t. $activates[0]\n";
> + deactivate_help();
> exit (1);
> } else {
> my $rec_activate = "$virtenv_dir/bin/activate";
> @@ -697,6 +704,7 @@ sub check_needs()
> printf "\t$virtualenv $virtenv_dir\n";
> printf "\t. $rec_activate\n";
> printf "\tpip install -r $requirement_file\n";
> + deactivate_help();
>
> $need++ if (!$rec_sphinx_upgrade);
> }
Thanks,
Mauro
prev parent reply other threads:[~2019-09-18 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 22:48 [PATCH] scripts/sphinx-pre-install: add how to exit virtualenv usage message Shuah Khan
2019-09-18 9:29 ` Mauro Carvalho Chehab [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=20190918062921.73a45f2d@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rfontana@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
/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