Hi Johannes, hi all, On Sat, Oct 11, 2003 at 02:24:16PM +0200, Johannes Winkelmann wrote:
Hi Jürgen,
On Fri, Oct 10, 2003 at 20:09:01 +0200, Juergen Daubert wrote:
Hi all,
just in case someone is using it, attached a new version of the ck4up utility. No fancy new features, but code-cleanup and the possibility to nest "macro" definitions. Great. I'm using ck4up to check for updates and it works perfectly. I'd even suggest to create a port for this as monitoring a web site for changes is a task others probably want as well :-)
Johannes, thanks for testing and for your kind words. I'll try to put together a man-page and a port for ck4up.
For my personal taste I'd prefer the data dir to be hidden (think: $HOME/.ck4up) and automatically created if it doesn't exists. Rationale: as the only file the user has to create is the ck4up.conf, it doesn't seem obvious to me the she/he has to create a directory first; the DB is an internal affair and Joe User shouldn't care about it.
This is just an idea though :-) (plus an attached patch)
Good ideas ! Both will go into the next version, and thanks for the patch.
I've included a macro @FM@ in the sample configuration file, which makes use of the freshmeat project XML database. With this, it's very lazy to add a line like 'crux md5 @FM@' to ck4up.conf and everything is done. cool!
btw, a good starting point for a ck4up.conf, using the @FM@ macro, could be the output of something like this: prt-get printf '%n\tmd5\t@FM@\t%M\n' | grep 'Jürgen' | cut -f1,2,3 Greetings Jürgen -- juergen.daubert@t-online.de