All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard W.M. Jones <rjones@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] kernel packaging split up landing in Rawhide
Date: Thu, 1 May 2014 18:18:43 +0100	[thread overview]
Message-ID: <20140501171843.GC26412@redhat.com> (raw)
In-Reply-To: <CA+5PVA7RTS1=TuSpBzFppTff9qoSr6MrhyyYBzcsoPS_cs4JMw@mail.gmail.com>

On Wed, Apr 30, 2014 at 07:56:29AM -0400, Josh Boyer wrote:
> Nothing at the moment.  Later this week I'm going to look at enabling
> auto-provides for kernel modules in the various kernel packages.  This
> will make situations like this much more flexible, as gfs2-utils will
> be able to Requires: gfs2.ko (or whatever it is) instead of the
> package name.  That will allow us to move modules around without
> breaking packages, and potentially get ride of k-m-e down the road.

That would be useful for libguestfs too.  It has a pretty well defined
list of kernel modules that it needs.

> Once the auto-provides are enabled, I'll go through the tracker bug
> Bruno has open and fix up the userspace package requires.

Which is the tracker bug?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW



  parent reply	other threads:[~2014-05-01 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+5PVA5aXe2T7c-fKkQtziQ5j=dog8LqcmJ3Md0y=ju1iyn-MA@mail.gmail.com>
2014-04-30  9:41 ` [Cluster-devel] kernel packaging split up landing in Rawhide Steven Whitehouse
2014-04-30 11:56   ` Josh Boyer
2014-04-30 12:53     ` Bruno Wolff III
2014-05-01 17:18     ` Richard W.M. Jones [this message]
2014-05-01 19:24       ` Bruno Wolff III
2014-05-01 19:37         ` Richard W.M. Jones

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=20140501171843.GC26412@redhat.com \
    --to=rjones@redhat.com \
    /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.