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=592670
--- Comment #13 from Rafael Aquini aquini@linux.com 2010-05-18 14:35:41 EDT --- Hello Terje, Ralf and Chen.
Firstly, thank you guys a lot for giving me such attention!
(In reply to comment #10)
Some more, more important comments:
o should the python bindings be shipped?
Could you point me some doc on that, please? I'm kind of python 'unaware' :(
o does it make sense to ship and enable a default mongonse.conf in /etc/mongoose.conf by adding -DCONFIG_FILE="%{_sysconfdir}/mongoose.conf" to make and install mongoose.conf in correct location?
OK, that will be done in the next Spec.
o ship .c and .h file in devel package for use in embedded mode?
Those were shipped in the first version, in a -devel rpm. Chen has pointed it as unnecessary and I stripped it off from Spec. I can reinclude the %package section and ship those files again.
o mongoose seems to do some funky things with SSL. There are no req. on ssl libs, but package seems to have SSL support.
In SSL mode, mongoose tries to load libssl.so on demand -- pretty much like apache does with its modules. It was my fault not include the libssl-devel req. My question, now, is that: Should I include this -devel req in the ordinary rpm or should I ship it as another rpm (like -ssl), just to fulfill this req, that users must install if they want SSL support?
(In reply to comment #12) Chen, as it seems that you ended up agreeing with Terje and Ralf, I will adopt your last suggestion and just use macros from now on (until we haven't another guidance).Please do not take it as personal, I just really think that macros are useful and cleaner than simple cmds.
Guys, thanks again! In a couple days I will be posting these new improvements...
Please, let me aware of anything else meanwhile!
Best regards.