All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Woodruff,
	Robert J"
	<robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	'Christoph Hellwig' <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Steve Wise
	<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
	'Leon Romanovsky' <leon-2ukJVAZIZ/Y@public.gmane.org>,
	'linux-rdma' <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	'Vladimir Sokolovsky'
	<vlad-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"Davis,
	Arlin R" <arlin.r.davis-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: rdma-core release?
Date: Wed, 12 Oct 2016 19:45:32 -0600	[thread overview]
Message-ID: <20161013014532.GA12670@obsidianresearch.com> (raw)
In-Reply-To: <ddda9ec9-1690-4d0a-07c8-980cac16304e-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, Oct 12, 2016 at 06:15:11PM -0400, Doug Ledford wrote:

> For someone like OFED this matters too because their scripts have to be
> made aware of all possible package names so they know to remove the
> inbox packages before they install their own.  For the foreseeable
> future, the OFED scripts will have to be aware of both a monolithic
> build and a split out build just so it can do the removal successfully.
> They are then free to install the packages however they see fit.

ofed may wish to consider just a very simple monolithic
rdma-core-{libs,devel,bin} which conflicts with all possible distro
package names...

Also, I hope that several of the 'loose' things ofed has like the init
scripts and what not will migrate into rdma-core and be more
consistent across distros. OFED may prefer to patch such things 
into rdma-core than to continue producing 'loose' stuff.

> There will be some education issues to resolve.  Even though we are
> likely to split up the package output on EL 7, there is not a 1 to 1
> correspondence.  For example, there will only be one debuginfo package
> for the entire build, so people who thought they could do yum install
> libmlx4-debuginfo are going to be wondering why it isn't available.  But
> there isn't much we can do about that.  Fortunately, it's only the
> debuginfo and src rpm that will change this way, we can create all of
> the other split out packages so things will look mostly the same way.

That should be doable, I was able to do it for Debian.

Do you think the new providers could go into some kind of combined rpm
in EL 7 with the same name that FC/EL 8 will have?

Ideally I'd like to get to a point where adding new providers is not a
pain point requiring distro approval and eval of new package names/etc.

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

      parent reply	other threads:[~2016-10-13  1:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 10:51 rdma-core release? Christoph Hellwig
     [not found] ` <20161012105103.GA30534-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-10-12 11:43   ` Leon Romanovsky
     [not found]     ` <CALq1K=JEkvN_4tZL9D53c6-EH9E4efay8rmoyBEyB-7Sxr6H-w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-12 13:00       ` Doug Ledford
     [not found]         ` <59ebde13-0fcd-0640-e750-bb6e57bfb921-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 14:43           ` Steve Wise
2016-10-12 16:31             ` 'Christoph Hellwig'
     [not found]               ` <20161012163149.GA20174-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-10-12 16:47                 ` Jason Gunthorpe
     [not found]                   ` <20161012164759.GB18838-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-12 17:37                     ` Leon Romanovsky
     [not found]                       ` <20161012173702.GW9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-12 18:15                         ` Doug Ledford
2016-10-12 18:17                     ` Woodruff, Robert J
     [not found]                       ` <9C6B67F36DCAFC479B1CF6A967258A8C7DE23B5D-8oqHQFITsIFqS6EAlXoojrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-10-12 18:35                         ` Jason Gunthorpe
     [not found]                           ` <20161012183548.GA31053-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-12 19:00                             ` Woodruff, Robert J
     [not found]                               ` <9C6B67F36DCAFC479B1CF6A967258A8C7DE23BA8-8oqHQFITsIFqS6EAlXoojrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-10-12 22:15                                 ` Doug Ledford
     [not found]                                   ` <ddda9ec9-1690-4d0a-07c8-980cac16304e-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-13  1:45                                     ` Jason Gunthorpe [this message]

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=20161013014532.GA12670@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=arlin.r.davis-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=leon-2ukJVAZIZ/Y@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
    --cc=vlad-VPRAkNaXOzVWk0Htik3J/w@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.