patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] filenames of DPDK stable packages
Date: Tue, 24 Jul 2018 11:12:56 +0200	[thread overview]
Message-ID: <5213154.30SCDzBaau@xps> (raw)
In-Reply-To: <1532365653.7624.9.camel@debian.org>

Hi,

23/07/2018 19:07, Luca Boccassi:
> On Tue, 2018-07-17 at 13:34 +0000, Richardson, Bruce wrote:
> > 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"?

This is what the hook is doing:

    for ext in gz xz ; do
        echo "generating tarball dpdk-$ver.tar.$ext..."
        wget http://dpdk.org/browse/dpdk-stable/snapshot/dpdk-stable-$ver.tar.$ext
        mv -f dpdk-stable-$ver.tar.$ext /srv/rel/dpdk-$ver.tar.$ext
    done
    echo "MD5 (to copy in HTML page)"
    md5sum /srv/rel/dpdk-$ver.tar.xz

> 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?

All is possible.

I am not in favor of having two copies with different names because it
would bring more questions.

When listing tarballs, it is easier to have the same prefix for all:
	http://fast.dpdk.org/rel/

We could rename the directory inside the tarball but we would have
a different checksum compared to the one in cgit:
	http://git.dpdk.org/dpdk-stable/refs/

Or we could change the prefix in cgit with repo.snapshot-prefix:
	https://git.zx2c4.com/cgit/tree/cgitrc.5.txt#n590
However I guess it would change every old tarballs.

Opinions?

  reply	other threads:[~2018-07-24  9:13 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
2018-07-24  9:12   ` Thomas Monjalon [this message]
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=5213154.30SCDzBaau@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=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).