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 20:37:40 +0100	[thread overview]
Message-ID: <20140501193740.GU1302@redhat.com> (raw)
In-Reply-To: <20140501192414.GA32221@wolff.to>

On Thu, May 01, 2014 at 02:24:14PM -0500, Bruno Wolff III wrote:
> On Thu, May 01, 2014 at 18:18:43 +0100,
>   "Richard W.M. Jones" <rjones@redhat.com> wrote:
> >
> >Which is the tracker bug?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1058331
> 
> I added everything that depended on kernel_modules_extra. There
> might be other things that should be changed, that depend on modules
> that are currently in kernel-drivers in case the modules move from
> one to the other.

Thanks.  I think that particular bug isn't relevant to libguestfs.

Adding 'Requires: foo.ko, bar.ko' will be possible.  Whether it will
make libguestfs pull in a smaller kernel sub-dependency is unlikely.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org



      reply	other threads:[~2014-05-01 19:37 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
2014-05-01 19:24       ` Bruno Wolff III
2014-05-01 19:37         ` Richard W.M. Jones [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=20140501193740.GU1302@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.