From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: 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,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce removal of interactive setup script
Date: Thu, 06 Aug 2020 19:02:20 +0200 [thread overview]
Message-ID: <3092143.TYmxAG33DM@thomas> (raw)
In-Reply-To: <20200806095635.20eb8d5e@hermes.lan>
06/08/2020 18:56, Stephen Hemminger:
> On Thu, 06 Aug 2020 18:25:23 +0200
> Thomas Monjalon <thomas@monjalon.net> wrote:
>
> > 06/08/2020 18:23, Stephen Hemminger:
> > > 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
> > > > ---
> > > > +* 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.
> >
> > Yes we could do that if this deprecation is accepted (missing an ack).
>
> Never liked dpdk-setup.sh anyway
Me too
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied
prev parent reply other threads:[~2020-08-06 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 10:26 [dpdk-dev] [PATCH] doc: announce removal of interactive setup script 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
2020-08-06 16:25 ` Thomas Monjalon
2020-08-06 16:56 ` Stephen Hemminger
2020-08-06 17:02 ` Thomas Monjalon [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=3092143.TYmxAG33DM@thomas \
--to=thomas@monjalon.net \
--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=stephen@networkplumber.org \
/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.