Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=635511 --- Comment #33 from Tim Niemueller <tim@xxxxxxxxxxxxx> 2011-03-24 04:36:35 EDT --- Excellent, I'll try with OpenRAVE later. For the shared-lib-calls-exit thing: please consider asking upstream to either have a release mode which is silent about the error (and a debug mode where this exits) or to throw a std::exception which can be caught on software embedding assimp simply reporting a load error. I'd assume assertions are used for "static" errors, i.e. not-so-dynamic errors which either happen or don't and if then they appear in the development phase, rather than using them for simple value range checks etc., which should be reported as soft errors to the caller. Is that the case? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review