DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com,
	arybchenko@solarflare.com, ferruh.yigit@intel.com,
	bruce.richardson@intel.com, ajit.khaparde@broadcom.com,
	jerinj@marvell.com, maxime.coquelin@redhat.com,
	akhil.goyal@nxp.com, bluca@debian.org, ktraynor@redhat.com,
	honnappa.nagarahalli@arm.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce removal of interactive setup script
Date: Thu, 6 Aug 2020 09:23:31 -0700	[thread overview]
Message-ID: <20200806092331.4b5e5113@hermes.lan> (raw)
In-Reply-To: <20200806145150.3529482-1-thomas@monjalon.net>

On Thu,  6 Aug 2020 16:51:50 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> Environment configuration is the responsibility of distributions
> or upper-level frameworks.
> DPDK focus on documenting the requirements and some recommendations.
> If some specific parts are complex, they can deserve some scripts.
> 
> Maintaining a good adaptative deployment setup is a project by itself.
> Anyway this script was interactive, useful only for experimenters.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> v2: suggest replacing with more specific scripts
> ---
>  doc/guides/rel_notes/deprecation.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 1a07f88172..fb405a09ac 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -232,3 +232,8 @@ Deprecation Notices
>    Python 2 support will be completely removed in 20.11.
>    In 20.08, explicit deprecation warnings will be displayed when running
>    scripts with Python 2.
> +
> +* dpdk-setup.sh: This old script relies on deprecated stuff, and especially
> +  ``make``. Given environments are too much variables for such a simple script,
> +  it will be removed in DPDK 20.11.
> +  Some useful parts may be converted into specific scripts.

Do you want to add a nag at startup of dpdk-setup.sh in 20.08?
Users don't always read the deprecation notices.

  reply	other threads:[~2020-08-06 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 10:26 [dpdk-dev] [PATCH] " Thomas Monjalon
2020-08-04 10:30 ` Maxime Coquelin
2020-08-04 10:33   ` Jerin Jacob
2020-08-05 16:19 ` Ferruh Yigit
2020-08-05 16:26   ` Thomas Monjalon
2020-08-05 17:46     ` Trahe, Fiona
2020-08-05 18:26       ` Stephen Hemminger
2020-08-06  9:35         ` Bruce Richardson
2020-08-06 13:51           ` Kinsella, Ray
2020-08-06 14:43             ` Thomas Monjalon
2020-08-06 14:51 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2020-08-06 16:23   ` Stephen Hemminger [this message]
2020-08-06 16:25     ` Thomas Monjalon
2020-08-06 16:56       ` Stephen Hemminger
2020-08-06 17:02         ` Thomas Monjalon

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=20200806092331.4b5e5113@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=arybchenko@solarflare.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).