From: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>
To: "Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org"
<Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
"jthumshirn-l3A5Bk7waGM@public.gmane.org"
<jthumshirn-l3A5Bk7waGM@public.gmane.org>
Cc: "jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org"
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
"nmoreychaisemartin-IBi9RG/b67k@public.gmane.org"
<nmoreychaisemartin-IBi9RG/b67k@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma-core rpm for SuSE
Date: Thu, 3 Aug 2017 15:49:13 +0000 [thread overview]
Message-ID: <1501775351.2922.5.camel@wdc.com> (raw)
In-Reply-To: <20170803113505.GF4333-qw2SdCWA0PpjqqEj2zc+bA@public.gmane.org>
On Thu, 2017-08-03 at 13:35 +0200, Johannes Thumshirn wrote:
> On Thu, Aug 03, 2017 at 11:12:18AM +0000, Amrani, Ram wrote:
> > Hi Jason,
> > I see folders with rpm creating scripts for Debian and Red Hat.
> > How is a SuSE rpm generated?
>
> Please have a look at:
> https://build.opensuse.org/package/show/science:HPC/rdma-core
Hello Johannes,
Sorry but my opinion is that users should not have to rely on out-of-tree
patches to build an rdma-core RPM for SuSE systems. BTW, the script that I
use myself to build a SuSE rdma-core RPM is as follows:
#!/bin/bash
rpmtopdir=$PWD/rpmbuilddir
name=rdma-core
version=$(sed -n 's/^Version:[[:blank:]]*//p' rdma-core.spec) &&
rm -rf "${rpmtopdir}" &&
mkdir -p "${rpmtopdir}"/{BUILD,RPMS,SOURCES,SPECS,SRPMS} &&
git archive --prefix "rdma-core-${version}/" --output "${rpmtopdir}/SOURCES/${name}-${version}.tgz" HEAD &&
rpmbuild --define="%_topdir ${rpmtopdir}" -ba ${name}.spec
Bart.--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-03 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 11:12 rdma-core rpm for SuSE Amrani, Ram
[not found] ` <CO2PR07MB25846E91BD9DA1744AEB20BBF8B10-0HVHVVMgGXp9MDTzla2L+OFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-08-03 11:35 ` Johannes Thumshirn
[not found] ` <20170803113505.GF4333-qw2SdCWA0PpjqqEj2zc+bA@public.gmane.org>
2017-08-03 15:49 ` Bart Van Assche [this message]
[not found] ` <1501775351.2922.5.camel-Sjgp3cTcYWE@public.gmane.org>
2017-08-03 15:59 ` Nicolas Morey-Chaisemartin
[not found] ` <66a7dd28-f752-b8d9-e8c2-00128245ce2c-l3A5Bk7waGM@public.gmane.org>
2017-08-03 17:01 ` Jason Gunthorpe
2017-08-03 17:14 ` Bart Van Assche
[not found] ` <1501780444.2922.10.camel-Sjgp3cTcYWE@public.gmane.org>
2017-08-03 17:29 ` Jason Gunthorpe
[not found] ` <20170803172957.GA30952-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-08-04 5:55 ` Nicolas Morey-Chaisemartin
2017-08-03 19:08 ` Amrani, Ram
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=1501775351.2922.5.camel@wdc.com \
--to=bart.vanassche-sjgp3ctcywe@public.gmane.org \
--cc=Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=jthumshirn-l3A5Bk7waGM@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nmoreychaisemartin-IBi9RG/b67k@public.gmane.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