Installing kernel-<version>.src.rpm under my own build root

[John Summerfied]

Robert L Cochran wrote:
>

>>> For a kernel build, does doing this make sense? Or should I be 
>>> installing
>>> to /usr/src/redhat/SOURCES and /usr/src/redhat/SPECS?
I think that's never a good idea

>>
>>
>>
>> It depends. ;) Why are you installing the kernel source RPM?
>>
>> For a single-user box, you can just chown /usr/src/redhat to your 
>> packaging identity and do all packaging under the system default 
>> packaging tree. If you have multiple packagers sharing a host, give 
>> each his own packaging tree in his home directory.
>>
>> "Installing" a source RPM is conceptually the same as unpacking a 
>> source tarball, in the sense that it's unpacking an archive that must 
>> then be passed through translators to convert it into a binary object 
>> suitable for installation. There's nothing special about the kernel 
>> source RPM that justifies giving it special treatment.
>>
>>
> I'm installing kernel source because I want to fool with the stacks 
> option needed by the ndiswrapper driver, which in turn may help 
> ndiswrapper to work correctly with the Buffalo AirStation WLI-CB-G54A 
> wireless network PC card I want to pop into my laptop. I also want to 
> fool with kernel builds for the heck of it. And finally, because these 
> will let me get a good measure of how fast my Athlon X2 dual core 
> processor is. And although I just have a single user system it seems 
> safer to do the build in my home directory. As I haven't done a kernel 
> build in at least a couple of years, I am sure I can be entirely wrong.

Good reasons all.
I generally create .rpmmmacros containing something like this:
%_topdir /home/summer/redhat

and create the necessary directories:
mkdir -p ~/redhat/{BUILD,RPMS,SOURCES,SPECS,SRPMS}






-- 

Cheers
John

-- spambait
1aaaaaaa at computerdatasafe.com.au  Z1aaaaaaa at computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/

do not reply off-list