The other CLanLib review is under bug 199630 .

Blocker : needs BR lua

Possible fault. You haved defined ARCH_CONFIG_FLAGS in the %ifarch construct and
passed to the configure line. On a non x86 machine, ARCH_CONFIG_FLAGS is
undefined which may upset things somewhat!

(In reply to comment #2)
> Blocker : needs BR lua
> 

Actually that would be tolua++-devel, but indeed I forgot that one I'll addit
together with other needed fixes once a full review has been done.

> Possible fault. You haved defined ARCH_CONFIG_FLAGS in the %ifarch construct
> and passed to the configure line. On a non x86 machine, ARCH_CONFIG_FLAGS is
> undefined which may upset things somewhat!
> 
> 

Being non-defined bash will expand it to an empty string, which is just waht we
want.

I just submitted clanbomber for review which uses this, might be handy for
testing, see bug 199732

I can't get this application to compile. When it runs through the configure
script, it reports that it needs Hermes-1.3.0 or newer.

You'll need to find and submit Hermes-1.3.0 (or newer) and add that (and
tolua++-devel) to the BRs

??? I could have sworn I added Hermes to the BuildRequires. But appearantly I
forgot that one I'll add it (and tolua++) together with other needed fixes once
a full review has been done.

To get it for the review just do "yum install Hermes-devel", its already in Fe
with a capatial H

It'll now build and rpmlint is happy with all of the packages created.

I've made the alterations to the spec file so both tolua++-devel and
Hermes-devel are in the BRs and will get back to you on how it works under mock.

Can you also make the BR alteration changes and upload the new spec file?

One other thing. You have provides: clanlib06 = {version}-{release}. That's
okay, but why is it clanlib06 and not ClanLib06 as the spec file and other
references inside the spec file call it?

mock build fails : line 45 autoconf : command cannot be found

(In reply to comment #7)
> One other thing. You have provides: clanlib06 = {version}-{release}. That's
> okay, but why is it clanlib06 and not ClanLib06 as the spec file and other
> references inside the spec file call it?

Since it _is_ ClanLib06 it will automaticly provide CLanLib06, the lowercase
provide is there exactly for what it is to provide a lowercase alternative to
people who prefer all lowercase names. The guidelines have recently been updated
saying that its ok to have names containing uppercase when upstream uses
uppercase consistenly, but that a full lowercase provides should be present. The
reasoning behind this was to stop problems like you where having with _H_ermes.

About autoconf, missing BR. Sorry about all these missing BR's if I had a better
internet conenction myself I would try things in mock myself :|

Anyways here is a new version which hopefully will build in mock:

Spec URL: http://people.atrpms.net/~hdegoede/ClanLib06.spec
SRPM URL: http://people.atrpms.net/~hdegoede/ClanLib06-0.6.5-2.src.rpm

Changes:
* Sun Jul 23 2006 Hans de Goede <j.w.r.degoede> 0.6.5-2
- Add missing BRs: tolua++-devel, Hermes-devel and autoconf

I've found a problem when running on i386-devel with default SELinux settings.

Here is a new release which fixes this (in combination with a soon to be pushed
new Hermes):

Spec URL: http://people.atrpms.net/~hdegoede/ClanLib06.spec
SRPM URL: http://people.atrpms.net/~hdegoede/ClanLib06-0.6.5-3.src.rpm

Changes:
* Sun Jul 23 2006 Hans de Goede <j.w.r.degoede> 0.6.5-3
- Mark asm files as NOT needing execstack, making us OK with new default
  SELinux targeted policy settings.

rpmlint is warning me the src.rpm is mod 0666 instead of 0664 for the spec file

One thing I did notice during the build and that is debugging is turned off
while building, yet a debuginfo package is available. Surely this should not occur.

(In reply to comment #11)
> rpmlint is warning me the src.rpm is mod 0666 instead of 0664 for the spec file
> 
Strange I'll fix that before import.

> One thing I did notice during the build and that is debugging is turned off
> while building, yet a debuginfo package is available. Surely this should not
occur.
> 

This means that special debugging checks and printf have been turned off, even
without these extra checks it is still usefull to have a package with the
addresses of symbols and line number <-> asm offsets table, so that one can
descently run it through a debugger, that is what debuginfo packages are for.

mock built the package without a hiccup. As long as you fix the spec file, I'm
happy for this to be released

APPROVED

Thanks!

Imported and build, closing.