I might try this (IIRC< epoptai's done this with framechat already): post v.1 in Craft and include (in the comment body) a link to your home node or possibly directly to a location from which the latest version can be downloaded. 'Course, you'll need a stable, reliable connection for that.

Update No, I guess epoptai hasn't done that (yet, anyhow =)

Three cheers for the "Generosity" bit =)

perl -e 'print "How sweet does a rose smell? "; chomp $n = <STDIN>; $r
+ose = "smells sweet to degree $n"; *other_name = *rose; print "$other
+_name\n"'
[download]

framechat does have the ability to check for an updated version of itself on perlmonks as arturo suggests.

This is done by providing a link on the help page that compares the script's version info with a hidden tag on a small node containing the current version info. reputer also has this feature.

Update: deprecated asks for elaboration:

The script contains the following hash:

my%info = ( version => '1.2', date => '20010510' );
[download]

A small node on perlmonks contains the following HTML comment:

<!--INFO:version=1.1,date=20010415-->
[download]

To check for an update, the user clicks a link that downloads the version node and compares it with the %info hash, if they differ a message with links to the new code appear. See the source links above for the code that does it.

Perhaps a similar strategy can be used for a module, but having it check at intervals.

'Course, you'll need a stable, reliable connection for that.

That shouldn't be a hard problem anymore for any PM user...

---

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

Your cause is also going to be helped by having a complete test suite corresponding to each package you're publishing. You can then enforce that any submissions need to pass the published tests, and that any newly submitted functionality needs to be covered by new tests. It also provides a backstop to help prevent your posting broken code.

What I was thinking about was something like [id://#####,date]. Having such a device, one could write a script that check for updates for the nodes he is subscribed to. Another possibility could be adding a smart link (e.g. [id://#####], last updated [id://#####,date]) in our homenode, so that we could check for updates simply logging in and looking at our homenode.

Update: We could also use a new tag, for example <update>, manually adding the date of the last update of the node. "Subscription scripts" could be written as easily as described above, I suppose.

Maybe create a node of sorts that interfaces with sourceforges cvs?