public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: Installing kernel headers in kvm-kmod
Date: Thu, 10 Dec 2009 22:36:43 +0200	[thread overview]
Message-ID: <4B215BDB.7000600@redhat.com> (raw)
In-Reply-To: <200912102026.34997.arnd@arndb.de>

On 12/10/2009 10:26 PM, Arnd Bergmann wrote:
> On Thursday 10 December 2009 17:14:40 Jan Kiszka wrote:
>    
>> Avi Kivity wrote:
>>      
>>> On 12/10/2009 06:42 PM, Jan Kiszka wrote:
>>>        
>>>> I've just (forced-)pushed the "simple" version with
>>>> /usr/include/kvm-kmod as destination. The user headers are now stored
>>>> under usr/include in the kvm-kmod sources and installed from there.
>>>>
>>>>          
>>> It's customary to install to /usr/local, not to /usr (qemu does the same).
>>>        
> Right. Specifically, an install from source should go to /usr/local/include
> by default, while a distro package should override the path to go to
> /usr/include, which the current version easily allows.
>
> This also means that qemu will have to look in three places now,
> /usr/local/include/kvm-kmod, /usr/include/kvm-kmod and /usr/include.
> Adding /usr/local/include probably doesn't hurt but should not be
> necessary.
>    

The only icky bit is that /usr/local/include/kvm-kmod will stick around 
after the user forgets about it and switches to the kernel headers.  I 
don't see a way around it (it's the generic uninstall problem), so I 
think we should just live with it.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-12-10 20:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 13:07 Installing kernel headers in kvm-kmod Anthony Liguori
2009-12-10 13:12 ` Avi Kivity
2009-12-10 13:35 ` Jan Kiszka
2009-12-10 14:50   ` Arnd Bergmann
2009-12-10 15:01     ` Avi Kivity
2009-12-10 15:25       ` Arnd Bergmann
2009-12-10 16:42         ` Jan Kiszka
2009-12-10 16:44           ` Avi Kivity
2009-12-10 17:14             ` Jan Kiszka
2009-12-10 20:26               ` Arnd Bergmann
2009-12-10 20:36                 ` Avi Kivity [this message]
2009-12-10 21:44       ` Anthony Liguori
2009-12-10 15:01     ` Jan Kiszka

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=4B215BDB.7000600@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=arnd@arndb.de \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox