Re: [Valgrind-users] rpm build errors w/ valgrind 2.0.0 and Red Hat 9

[Josef W. <Jos...@in...>]

On Monday 24 November 2003 15:42, ga...@sp... wrote:
> On 24-Nov-2003 Nicholas Nethercote wrote:
> > That's not acceptabel;  they are needed by some tools (eg. KCachegrind).
> > Can't they simply be added to valgrind.spec.in?
>
> yes. of course that is the other alternative.
>
> Normally header files would have gone in a "devel" rpm, but since there
> wasn't one, I was unaware of the need for these by some other tools.
>
> The proper solution would be to have a "devel" rpm and put these in that
> rpm.

Isn't it the job of the distributor/packager to correctly split up a
source package into one with the binary and a -devel one?
I thought that the *.spec file in source tar.gz is only a hint and *can* be 
used by a packager.

The given include files are needed to compile external skins/tools. So yes, 
they would be a candidate for a -devel package. But that's up to you.

Cheers,
Josef