webchanges Homepage

... as long as web changes.


webchanges - as its name says - gives you the ability to monitor parts of webpages for user-relevant changes. For each collection of webpages, the user has to write a so-called monitor file once. This file describes, which documents on the web belong to the collection being monitored, and which parts of these documents are relevant. A single relevant part of a document is called monitor.

To be pedantic, webchanges operates on the [X]HTML-parts of a webpage only (leaving images, animations, etc. out) and uses W3C’s XPath 1.0 embedded in its own language to select those relevant parts.

You might want to visit the project page at sourceforge, too.


Use the project RSS feed (especially project file releases) to stay tuned.


The first place you will definitely want to look at, is the webchanges wiki. Due to some dumb-ass spammer I was forced to make the wiki world-readable only for the present. Time will tell. Contributions to the wiki are really really welcome, just register and hop on board!

There also is a test page that may help you to get started verifying, if your installation of webchanges is working correctly


as pre-compiled package

Pre-compiled packages and archives can be downloaded at the download page.

as source tarball

  1. Source tarballs can be downloaded at the download page, too.
  2. Extract the source:
    tar xjf webchanges-*.tar.bz2
    cd webchanges-*

as source via Git

  1. Download the source from the Git repository (read-only):
    git clone git://webchanges.git.sourceforge.net/gitroot/webchanges/webchanges
    cd webchanges
  2. Execute some standard autotool commands (obviously you have to install them before):
    automake --add-missing --copy

It is also possible to browse the Git repository via http first. If you need more information about how to cope with Git, visit the corresponding Git page.


  1. Before compiling webchanges you should verify that your system meets the following dependencies:
    • libxml2 (≥ 2.6.0)
    • wxWidgets (≥ 2.4.0) only if you want to build webchanges with GUI support.
  2. Configure webchanges:
    • If you want to install webchanges to the default prefix (usually /usr/local) later, just do something like this:
    • If you want to install webchanges to a different prefix, later, do something like this:
      ./configure --prefix=$HOME/local
      to prepare webchanges for being installed to ~/local/{bin,share} later.
    • If you want to enable the wxWidgets GUI, do something like this:
      ./configure --enable-gui
    • To get a full listing of all available configure options do:
      ./configure --help
  3. Compile and install webchanges the usual way:
    make install
    Of course you will need write permissions in the directory you specified before.


Post questions, bugs, remarks, patches, etc. to the corresponding pages at sourceforge to make them available to others.

Copyright © 2006-2008 Marius Konitzer