From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A0840A0524; Fri, 27 Nov 2020 15:12:11 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 09FD5C980; Fri, 27 Nov 2020 15:12:10 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 36A3CC972; Fri, 27 Nov 2020 15:12:07 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id CF9F75C00CA; Fri, 27 Nov 2020 09:12:05 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 27 Nov 2020 09:12:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= 05Y+39fJMPgaH2LqRQrUqLvg+AVpGoa0ci5ID54JmbY=; b=RznKj7kqFWaugSYS DDxcbGcB2dc7jNuUaQC0WBXWrhZSN8rpWZ8yFMSBJylwx4N3AyI+r6d5tQoThtyg xXHQyJnt5KrAnxAg4/5UNBU/p+0LDuH+coaz+Ywjo+CFzUXcXvBkxIRX+dS3DEOr CgZ/ACc0aFB5VPA9Buv2HQZYxPkHx2AzwiL4ygCxt6DPGwuH8Q+VGgoxfFgax1Cz JKIgjzBLDXd1O7Z1j83YdvzecItFovhrxPncf4t9MiVnRJZik8lANjsiyoccBTVW PgrD57FcwNWp4HW47FKpQLHhf+MrehwTsh52CkVwRxupxrFC2eXIlXUv8DfkY05l d0IM9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=05Y+39fJMPgaH2LqRQrUqLvg+AVpGoa0ci5ID54Jm bY=; b=bvUkUHahF0Wh8jZfu5GMIQjPIu5vXWOJdA7Qq4Vh8T5qldXlns7Q35XCK gNU7ld4+odPJIqSj7BnBw6BmqnRdmsWv/o2y03CvWATwazOBCunwPkkqO3eQJ1im EQIad4uaCKjaToTJceC3Yq1Vz23kWqyM7lLXwHopghde0MXWs1ifhVK+QN80XET0 YR9I/ICGvtJiw7qfE1NODCIjqNsilMJwImcBT+cntNh2vTcuNGAuXKBVgq15DnbS a7c6kAjuhBYTmy5YWpeF7GxSDbTHvy1f6nFN09RXp5CbAwljjWdZfj3VYSPFPFSY MBq6g8zUuUQlFwWu4DTFTuWhp8+XQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehgedgiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B68CD3280059; Fri, 27 Nov 2020 09:12:04 -0500 (EST) From: Thomas Monjalon To: Ferruh Yigit , "Burakov, Anatoly" Cc: dev@dpdk.org, techboard@dpdk.org, Stephen Hemminger , Bruce Richardson Date: Fri, 27 Nov 2020 15:12:02 +0100 Message-ID: <7186645.fz4gZY8XGM@thomas> In-Reply-To: <2970a852-d903-25fd-11ff-ca618f51905c@intel.com> References: <20201125191908.1867106-1-ferruh.yigit@intel.com> <2970a852-d903-25fd-11ff-ca618f51905c@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/6] update dpdk-setup.sh X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 27/11/2020 14:57, Burakov, Anatoly: > On 25-Nov-20 7:19 PM, Ferruh Yigit wrote: > > This is an effort to update the dpdk-setup.sh script and keep it one > > more year until whole functionality of it is replaced. > > > > Other option is to remove it completely, please comment. > > This script has been largely unmaintained for a long time, so my > personal opinion is that i'd rather see it removed. > > That said, i know for a fact that users (especially non-expert ones) > rely on this script, so removing it without providing a replacement is > not practical. This patchset IMO is a good first step towards bringing > the script up to date, but more work is needed as current usability of > the script is atrocious. I take it as one more argument to remove as planned in 20.11. Non-expert users should think before using this script. If they absolutely want it back they will take it from old versions, or they will complain, which is a kind of contribution, a first step to think about something better.