Ainsi parlait Rob Kudla :
> I have been packaging gambas, a GPL VB-like language with Qt as its
> toolkit, for a while and with its exit from alpha status I thought I would
> add it to contrib. However, gambas is kind of odd in that it has a two
> stage build: first it builds the C++ executables and components, and then
> it installs them to finish the build with the parts that are themselves
> written in gambas. I got around this by splitting it into two SRPM's from
> the same tarball, gambas and gambas-gui, the latter requiring the former,
You'd better use one single src package, and alternate build and install steps
of two stages. See how nessus package first build its librairies, install
them in rpm tmp directory, and build GUI next with just setting LD_LIBRARY
> but rpmlint prints a few dozen errors (besides warnings) in the following
> categories:
>
> 1. It thinks the gambas RPM is a library RPM (because the components, which
> are version-specific and will never be updated separately, are named
> lib.gb.* and go into /usr/lib) and doesn't like the lack of a library
> version and the presence of binaries. If there had to be a library package
> for every component included as part of the core Gambas package, there'd be
> dozens of packages by the time Gambas 1.0 rolled around.
>
> 2. It doesn't recognize the executables compiled into Gambas p-code as
> binaries. It may be that gambas-gui could be a noarch package, but I
> haven't confirmed that the final executables will actually run on non-x86.
bytecode is noarch by definition.
> 3. Various files from the original tarball are zero-length or have
> non-standard permissions like 744.
Just remove the empty files and fix perms, unless they are really useful.
--
Guillaume Rousse
Men's desire for sex sometimes results in intimacy.
Women's desire for intimacy often results in sex.
-- The Unintended Result
