Bug#139475: packaging of oprofile

[Al Stone <ahs3@fc.hp.com>]

Susan,

This whole day job can really slow down the Debian Developer
application process.  My apologies for the delays; if it gives
you any idea of how busy we've been, our little ol' Linux lab
has recently doubled in size -- and we plan on growing further.
Long nights and weekends have been de rigeur.

If one was to go to:

   ftp://ftp.hp.com/pub/linux/prospect/

one would find the latest prospect packages (0.9.7-3), and
the latest oprofile packages:

   -- oprofile 0.5.4-2 (ia64, i386)
   -- oprofile-source 0.5.4-2 (ia64, i386)

as well as some pre-built kernel modules:

   -- oprofile-modules-2.4.20-1-686_0.5.4-2_ia64.deb
   -- oprofile-modules-2.4.20-mckinley-smp_0.5.4-2_ia64.deb

Everything has been updated to the latest upstream source.
In the oprofile-source packages, there are now HOWTO docs
in /usr/share/doc/oprofile-source with detailed instructions
on how to build kernel modules (with, and without, make-kpkg).
All the various source pieces are at the same ftp site.

Due to a need for automake1.7 in the new upstream, as well
as kernel version requirements (>2.4.18), these packages will
not build nor will they work properly for stable releases on
either i386 or ia64.  There are a couple of other architectures
supported by oprofile, but I don't have machines to build on
or test on.

Let me know when you get a chance to look at these, and/or
test them.  Holler if there's any bugs or clarification that
I can include.

Thanks in advance for your time and effort -- and most
espcially, your patience.

On Tue, 2003-03-25 at 12:44, Susan Kleinmann wrote:
> 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
-- 
Ciao,
al
----------------------------
Al Stone
Linux & Open Source Lab
Hewlett-Packard Company
Phone:  970-898-0345
Telnet:     898-0345
Fax:    970-898-3804
E-mail: ahs3@fc.hp.com
----------------------------