On Thu, Feb 20, 2003 at 12:18:45PM -0600, Gilles Detillieux wrote: > While looking for Gabriele's cookies patch, I stumbled upon this long > forgotten message...
Thanks for checking in. :) I ended up copying and pasting the binary file from another web server (both debian installations). I put the instructions that I got from various people up on the language HOWTO that I did. Here they are in case anyone else needs the info. Please let me know of any corrections that should be made. I'll make them on the language HOWTO that I've got up. Copied from: http://xtrinsic.com/geek/articles/language.phtml Background This site also uses cookies. There were a number of problems trying to get the cookies patch to apply properly to the debian package htdig binary file. Ultimately I had to copy the htdig program (binary file) from another machine that had been compiled from source. For those of you who are curious, the v 3.1.6 htdig + cookies patch should give the following md5 hash md5sum htdig should give the output: 9237f812f9e30d6f482cffd0656304ed htdig. [Thanks Steve] Dealing With Cookies [there are links to the patches in this section which I haven't copied and pasted] I had to install the cookies patch to v 3.1.6 to keep htdig from crawling out of control. Here are some notes on installing that patch as well. To be honest, I had my sys admin do this for me...Although he was unable to get it to work and I ended up copying and pasting the binary from another installation that was built from source instead of from the debian package. I have NOT tested either of these two methods, however, I believe they make sense and should work. :) * The debian package does NOT seem to get along with this patch for * Woody + stable. It was completely fine on my lap top though (Woody + * unstable). YMMV. * The correctly patched htdig binary file is: 293572 (check with ls * -l) * First download the cookies patch (right click and Save This Link * As...). Once you've installed the patch, don't forget to add the following to your configuration file: * url_rewrite_rules: (.*)\\?SESSION=.* \\1 \ (.*)\\&SESSION=.* \\1 * disable_cookies: false How to install a patch The following instructions are from Neil Kohl. Thanks Neil! :) * To apply the patch you need the htdig source code on your machine * and you must have permission to modify and create files in the * source directory. * Download and uncompress the patch, then copy it to the top of the * htdig source tree. Then run the patch command from the top of the * htdig source tree. patch applies the patches contained in the file * to the appropriate source code files and is usually run like this: patch -b < patch-file-name * The -b flag creates backups of any files it touches with the * extension .orig. * After you've run patch, you have to recompile and install the htdig * binaries (run configure if you're never compiled this source before, * make all, make install as per the documentation). Patching on debian Nate gives the following debian-specific instructions. * download the debianized source of htdig debian htdig package * if you have source uris in /etc/apt/sources.list apt-get source htdig * if you don't have source uris, then when you get the source and the * patch, extract them, cd to the htdig directory and patch it with the * debian patch patch -p1 <../filename.diff * then patch the source with your patch: patch -p1 <../filename.diff * you may need to reverse the order of the patches if your patch fails * (patches can fail if another patch changes too much it may get lost * and not know what to patch). Assuming it patches correctly, and you * have a devel enviornment: apt-get build-dep htdig apt-get install fakeroot fakeroot ./debian/rules binary * (if you downloaded the debian patch manually you'll probably have to * chmod +x debian/rules first) * if it all works out you should have one or more .deb's built at the * end .. * ask the admin to install them, but they also should mark the * packages as held, otherwise the package system may automatically * overwrite them: dpkg --get-selections >selections (edit selections, find htdig, change install to hold) dpkg --set-selections <selections > As far as I know, they're both the same patch. (Note to Joe: it might > make more sense to call it cookies.0.gz instead of cookies.gz.0.) Yea, it's just Joe's version of Gabriele's patch. The 0 has significance that was explained to me at one point, but I can't remember what it was now. (Version control, maybe?) > Generally for a patch, you put yourself in the main souce directory and > then run a command like "patch -p0 < name-of-patch-file", or use -p1 if > the patch has an extra level of directory names in the target file names. > In the case of a compressed patch like this one, you can use: > zcat cookies.gz.0 | patch -p0 Your instructions are essentially backwards from the ones I got (cat first, vs use > to output the actions of "patch")...I think? > I don't recall seeing a followup to your questions before, but you haven't > repeated the request, so my apologies if it's now a moot point. /grin/ Yah, I usually repeat questions after much puttering if I still can't figure it out. Thanks again for the follow up, I appreciate it!! -- Emma Jane Hogbin [[ 416 417 2868 ][ www.xtrinsic.com ]] ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
