From now on I will always include the CVS code on which the patch was based to get around these irritating synchronisation problems.
Indan, if you want to update your HTTPS patch, may I suggest you use this source code tarball instead of current Dillo CVS? This way we are less dependent on the state of CVS...
I use the -D option in my install script, and I rewrote the thing so I could just give the date at the top and it will download and install the correct CVS and patches, but now that won't work... To make matters worse, I also updated my https code to the current CVS (which didn't change for two days..). I would appreciate it a lot if you make a patch against the current state of CVS and give the file the usual name. I use FILE1="dillo-${YEAR}${MONTH}${DAY}-tabs.patch.gz" in my script, so it's very easy to update when there's a new version. I could add hours and minutes, but I'd rather leave those out, and when you make a updated version, I also don't have to "downdate" my code/patch. Another possibility is that you make a link named dillo-$DATE-tabs.patch.gz where DATE is the date of the Dillo CVS version that works with your patch, and points to the dillo-$RELEASE_DATE-tabs.patch.gz file. You don't have to host the Dillo source you used, not for me anyway, I won't use it, all I need to know is the date of the CVS you used, and sometimes the time too ;-). I think the install script causes more exposure, because it makes it very easy to get a patched Dillo; people don't even have to know what CVS is. The new https patch will be out soon, maybe even today, so you may expect a new installer soon. Greetings, Indan