From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] doc: including_bsp_doc: add missing virtualenv command
Date: Tue, 9 Oct 2018 13:14:19 +0200 [thread overview]
Message-ID: <20181009111419.cckczhgduj533t3e@pengutronix.de> (raw)
In-Reply-To: <20181009110041.4lpc3dtfgelzymje@pengutronix.de>
On Tue, Oct 09, 2018 at 01:00:41PM +0200, Michael Olbrich wrote:
> On Tue, Oct 09, 2018 at 12:36:40PM +0200, Robert Schwebel wrote:
> > On Tue, Oct 09, 2018 at 11:20:01AM +0200, Ahmad Fatoum wrote:
> > > otherwise, there wouldn't be an env/ directory to source inside.
> > > ---
> > > doc/including_bsp_doc.inc | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/doc/including_bsp_doc.inc b/doc/including_bsp_doc.inc
> > > index cfccc45b4e80..b7a986f5d547 100644
> > > --- a/doc/including_bsp_doc.inc
> > > +++ b/doc/including_bsp_doc.inc
> > > @@ -32,6 +32,7 @@ when not globally present in the host system.
> > > .. code-block:: text
> > >
> > > $ pip3 install --upgrade --user pip virtualenv
> > > + $ virtualenv env
> >
> > Since python 3.6, virtualenv is deprecated and you should use
> >
> > $ python3 -mvenv env
> >
> > https://docs.python.org/3/library/venv.html
>
> Ok, but the only thing that changes are the commands to create the
> virtualenv, right? Activation remains the same?
Yes.
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-10-09 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 9:20 Ahmad Fatoum
2018-10-09 10:36 ` Robert Schwebel
2018-10-09 11:00 ` Michael Olbrich
2018-10-09 11:14 ` Robert Schwebel [this message]
2018-10-11 12:36 ` Ahmad Fatoum
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=20181009111419.cckczhgduj533t3e@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=ptxdist@pengutronix.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