patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: thomas@monjalon.net
Subject: Re: [dpdk-stable] filenames of DPDK stable packages
Date: Mon, 23 Jul 2018 18:07:33 +0100	[thread overview]
Message-ID: <1532365653.7624.9.camel@debian.org> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B072664923@IRSMSX103.ger.corp.intel.com>

On Tue, 2018-07-17 at 13:34 +0000, Richardson, Bruce wrote:
> 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

Hi Bruce,

It would be perfectly fine to me to have an additional copy of the
tarball, however all we maintainers do is push a tag, then the cgit
server does all the magic. The directory name I guess it's based on the
git root directory name on the server.

Thomas, any idea how to do what Bruce is asking?

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-07-23 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 13:34 Richardson, Bruce
2018-07-23 17:07 ` Luca Boccassi [this message]
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=1532365653.7624.9.camel@debian.org \
    --to=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=stable@dpdk.org \
    --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).