"eps com estem" <[EMAIL PROTECTED]> writes: > After browsing through /apreq_params.c i've noted that the code lines > indicated to be changed are apparently not changed (so the bug is > there still). Then, the questions: > > a) Is not the available code to download from the web page upgraded > with this changes?
Only from the snapshots of apreq's subversion trunk. Most of the recent work towards a 2.05-dev release is happening in a branch. Lots of excellent feedback has come back from the 2.04-dev release, and hopefully 2.05-dev will address all the known issues. > b) I don't know very well what to do with the changes noted in last > mails (i.e. what that notation means), is there any doc about it out there? I think you're referring to `diff` output? If so, look for documentation on the standard *nix `patch` and `diff` utils. > c) Once compiled apache+libapreq2+mp2, if i want to compile a new > version what is the protocol? to uninstall everything and to reinstall > again?? (this is a linux basic question, i know, therefore it is an > offtopic, but any help will be appreciated) If you're building mp2 and apreq2 as typical *nix DSOs (not static builds), you shouldn't need to recompile everything; just upgrade each component as you see fit, and the others should still work ok. You should only need to recompile the others when you want to upgrade apache from 2.0.x to 2.2.x. -- Joe Schaefer
