DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/4] recipes for RPM packages
Date: Wed, 30 Apr 2014 02:46:41 +0200	[thread overview]
Message-ID: <1398818805-18834-1-git-send-email-thomas.monjalon@6wind.com> (raw)

The goal of this patch serie is to be able to package DPDK
for RPM-based distributions.

The file naming currently doesn't allow to install different DPDK versions.
But the packaging naming should be ready to manage different DPDK versions
having different API/ABI for different applications:
	- dpdk-core has full version in its name to manage API breaking
	- extensions have a number as name suffix to manage PMD API breaking.
When API/ABI will be stable, package names could be simpler.

I suggest to add these .spec files as a starting point for integration
in Linux distributions.

Changes since v1:
	- name of .spec file match package name
	- version in package name
	- no static library
	- ldconfig/depmod in scriplets

Thanks for your comments/reviews.
-- 
Thomas

             reply	other threads:[~2014-04-30  0:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  0:46 Thomas Monjalon [this message]
2014-04-30  0:46 ` [dpdk-dev] [PATCH v2 1/4] pkg: add recipe for RPM Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [memnic PATCH v2 2/4] " Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [vmxnet3-usermap PATCH v2 3/4] " Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [virtio-net-pmd PATCH v2 4/4] " Thomas Monjalon
2014-04-30 10:52 ` [dpdk-dev] [PATCH v2 0/4] recipes for RPM packages Neil Horman
2014-04-30 11:09   ` Thomas Monjalon
2014-04-30 15:22     ` Neil Horman
2014-05-01  6:53       ` Thomas Monjalon
2014-05-01 10:28         ` Neil Horman
2014-05-01 15:13           ` Thomas Monjalon
2014-05-01 13:14 ` Neil Horman
2014-05-01 21:15   ` Thomas Monjalon

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=1398818805-18834-1-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@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).