#8 Fedora 10 Packaging

[AnotherUser]

I am currently attempting to package this for Fedora 10. As such, there are several thinks which I should, from a maintainers point of view, notify you about.

1) The licence file "COPYING" accompanying the package is in fact empty, even though the source files themselves are clear as to the licence.

Fedora packagers (me) are encouraged to contact upstream (you) in order to get a full copy of the licence included in the package.
https://fedoraproject.org/wiki/Packaging/LicensingGuidelines#License_Text

2) The libraries
*libnurbsd
*libnurbsf

Call the exit() function, which was detected by an automatic package checking utility. I have provided the output from this utility below.

nurbs++.i386: W: shared-lib-calls-exit /usr/lib/libnurbsf.so.0.1.0 exit@GLIBC_2.0
This library package calls exit() or _exit(), probably in a non-fork()
context. Doing so from a library is strongly discouraged - when a library
function calls exit(), it prevents the calling program from handling the
error, reporting it to the user, closing files properly, and cleaning up any
state that the program has. It is preferred for the library to return an
actual error code and let the calling program decide how to handle the
situation.

nurbs++.i386: W: shared-lib-calls-exit /usr/lib/libnurbsd.so.0.1.0 exit@GLIBC_2.0
This library package calls exit() or _exit(), probably in a non-fork()
context. Doing so from a library is strongly discouraged - when a library
function calls exit(), it prevents the calling program from handling the
error, reporting it to the user, closing files properly, and cleaning up any
state that the program has. It is preferred for the library to return an
actual error code and let the calling program decide how to handle the
situation.

If it is possible to alter the library code such that it does not call the exit() function, this would be good from a maintainer view.

3) In order to allow for the source code to compile under fedora, extensive patching has been required for GCC 4.3; If it is possible to merge one of the three packages that are listed in your tracker with your main release, checking for their validity, this would also be greatly appreciated, and would improve the quality of the final package.

Thankyou