It is as if the devil plays with it... 5 minutes after I upload my latest patches, CVS gets updated and the patch does not apply anymore.
Oh so funny. :) I saw you updated your patch today, and the first thing I thought was: Why didn't Frank say that he used the CVS version of yesterday, because CVS didn't change for two days, and _if_ CVS would be updated today, there will be problems. So, the easy sollution is to rename your patch to "dillo-20031120-tabs.patch.gz" and everything will work just fine. Although not with the current CVS of course, but that will happen anyway if you wait long enough. Are the recent changes worth it to update your patch, that's the question. Apparently you already did that, but there is no reason to include the whole source. What Thorben said is exactly what my installer script does; the -D option is nice. Offtopic: Could you reply to the CVS offer from Trent Jarvi and say what you think about a CVS branch? See: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-November/001470.html I think a seperate CVS branch would be useful, one hosted by the same server as the official Dillo CVS, or an external one, like Trent's. Where doesn't matter much I guess. At least the patches are centralized then.