Bug#139475: packaging of oprofile

[Susan Kleinmann <sgk@kleinmann.com>]

Hello Al,

On Tue, 25 Mar 2003 10:35:14 MST, Al Stone <ahs3@fc.hp.com>  said: 
> can one make any assumptions
> about the state of the kernel source tree when
> providing a package?  For instance, will all the
> variations of oprofile modules be built for all of
> various kernels available, 
I would expect that (since the oprofile modules are being built from the
top level of a single source tree, and since that source tree has only one
file named ".config" in it) only one set of oprofile modules would be built
when 'make-kpkg modules_image' is executed.
> or do I have to build them?  
> If the former is true, can I reasonably
> assume that 'make-kpkg config' has already been
> run?  
I think the build script should just test for the existence of 
the file '.config' in the current directory.  (It might previously execute
some test to make sure it is really in the top level of a Linux kernel source
directory; this directory has many "signautures" but I don't know which one
is definitive, if any.  If the file isn't found, then the build script
should just exit with the message that one needs to run
'make config' or 'make menuconfig' or 'make xconfig'
or 
'make-kpkg --config (oldconfig|config|menuconfig|xconfig) 

(but not 'make-kpkg config') first.

I'm not sure I'm understanding your question, so if that doesn't answer it,
let me know and I'll try again.

Susan