From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Knut Omang <knut.omang-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Benjamin Drung
<benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdma-core package version schema
Date: Wed, 11 Jan 2017 15:10:04 -0700 [thread overview]
Message-ID: <20170111221004.GA31081@obsidianresearch.com> (raw)
In-Reply-To: <1484139556.2191.48.camel-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Wed, Jan 11, 2017 at 01:59:16PM +0100, Knut Omang wrote:
> It seems that interface is only available for those with write
> access to the github repo which does not cover the (for me at least)
> common use case that I want to built my own slightly modified test
> .rpm of something. Then users will end up creating tarballs
> manually, or outside the build logic, with potentials for mistakes,
> not to mention the?? documentation need to tell users this.
Any user can run git archive and it will always create the correct
result.
$ git archive --prefix rdma-core/ --output rdma-core-12.tgz HEAD
No other steps are required.
> Isn't a dist target a well established standard the rdma_core packages should??
> support for simplicity and uniformity?
'make dist' is kinda a GNUism where packages that use auto* require
building pre-build auto* stuff into their tar files. We do not require
that and our dist tar file is identical to what git archive produces.
For developers we have the buildlib/cbuild script. Install docker and
it will automate building packages for you:
$ buildlib/cbuild build-images centos7 # One time
$ buildlib/cbuild pkg centos7
It takes care of all the details and guarantees the build is done with
the correct set of build time packages.
Jason
--
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-01-11 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 19:01 rdma-core package version schema Benjamin Drung
[not found] ` <1483642867.5227.18.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-01-05 23:09 ` Jason Gunthorpe
[not found] ` <20170105230928.GA4262-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-06 17:28 ` Benjamin Drung
[not found] ` <1483723704.5227.23.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-01-06 18:47 ` Jason Gunthorpe
[not found] ` <20170106184717.GC5724-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-08 8:51 ` Leon Romanovsky
2017-01-08 8:47 ` Leon Romanovsky
[not found] ` <20170108084759.GJ15685-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-11 12:59 ` Knut Omang
[not found] ` <1484139556.2191.48.camel-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-01-11 14:47 ` Leon Romanovsky
2017-01-11 22:10 ` Jason Gunthorpe [this message]
[not found] ` <20170111221004.GA31081-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-11 22:17 ` Knut Omang
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=20170111221004.GA31081@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=knut.omang-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.