On Thu, Apr 18, 2002 at 09:33:25PM +0200, Ralf S. Engelschall wrote:
> On Thu, Apr 18, 2002, Christoph Schug wrote:
> 
> > do you know what happened to the idea of having something like a
> > OpenPKG-lint program which does some tests on the .spec file and the
> > package (both binary and source) in general?
> > 
> > If it makes sense we should also add some checks to avoid DSO's as
> > well as non-striped binaries. In both cases this would be tests against
> > binary packages of course.
> > 
> > What do you think about it? Do we already have some lint tool flyin'
> > around and which can be enhanced this way?
> 
> I'm happy to see such a tool, because it is certainly a great idea
> and would help a lot. I also tried to write such a tool a few months
> ago when the idea popped up first. Unfortunately I was not successful
> because I discovered that the problem is a lot more complex than it
> looks at the first glance. But we should definitely try this again.
> 
> To be more successfully next time, we need first an exact list of what
> should be linted. Let's start brain-storming, guys (add your items):
> 
> o specification: exact indentations
> o specification: header (foo:) and section (%foo) ordering
> o binary RPM: not existence of shared objects under lib/
> o binary RPM: foo.N has to stay under man/manN/
> o binary RPM: bin/foo, sbin/foo and libexec/foo has to be stripped

You might like to take a look at Mandrake's rpmlint, it has a bunch of
good checks some of which are probably useful for cross-platform RPM
(though I'd expect the tool itself might need a lot of work for
cross-platform/relocatable RPMs). Off the top of my head, some of the 
checks it implements are

- no binaries outside bin, lib
- validation of %post/%pre/... scripts
- checks for RPATHs in binaries
- checks for zero-length files
- missing dependency between -devel package and it's master

Regards,

joe
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   [EMAIL PROTECTED]

Reply via email to