From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Subject: [dpdk-stable] filenames of DPDK stable packages
Date: Tue, 17 Jul 2018 13:34:38 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B072664923@IRSMSX103.ger.corp.intel.com> (raw)
Hi all,
looking to update the DPDK port in FreeBSD and was going to use the stable LTS trees rather than bleeding edge, but it proved more difficult than I would like because of filenames. The regular DPDK releases all use standard names, where "dpdk-x.y.tar.gz" unzips to a folder called "dpdk-x.y". However, for the stable releases like "dpdk-17.11.3.tar.gz", they unzip to a folder called "dpdk-stable-17.11.3" - i.e. the package name and unzipped names do not match. This is obviously something that can be worked around, but it's a bit of a pain.
Therefore a small ask - can we please provide a package for stable releases where the standard naming convention is used. I quite like having the "dpdk-stable" in the name, so perhaps as well as the regular tarball, could we also have a copy on the server called e.g. "dpdk-stable-17.11.3.tar.gz"?
Thanks,
/Bruce
next reply other threads:[~2018-07-17 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 13:34 Richardson, Bruce [this message]
2018-07-23 17:07 ` Luca Boccassi
2018-07-24 9:12 ` Thomas Monjalon
2018-07-27 17:15 ` Timothy Redaelli
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=59AF69C657FD0841A61C55336867B5B072664923@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=stable@dpdk.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 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).