Let the moonbase bitrot CHECK begin...

[Duncan Gibson]

During the discussion about the removal of the obsolete and unused(?)
gtk+ and gnome1 modules, Sofar suggested a yearly sweep of the Moonbase
to check for broken modules. I suggested adding a CHECKED field to the
details file so that users could tell which ones had already been done,
and when. There wasn't much feedback on the CHECKED idea, but there was
no violent disagreement either.

The idea is that modules which were last updated more than a year ago
are verified. If they are still current, and still work, then add the
current date to the CHECKED field, or if you need to make a non-version
change. If there is a new version, then obviously you change UPDATED as
usual. If it doesn't work, then report it on the bug-tracker.

For backwards compatibility, if there is no CHECKED date in DETAILS, it
is assumed to be the same as the UPDATED date.

To discover which are the most ancient UPDATED modules, you can either
sort on UPDATED field under the http://modules.lunar-linux.org/ page or
you can take a look at the attached check_updated.sh script. The script
works if you run it on a section by section basis, but fails with

    /var/lib/lunar/functions/modules.lunar: line 172: \
        /usr/bin/find: Argument list too long

if run on the complete moonbase. Debugging advice would be appreciated :-)

Cheers
Duncan / engelsman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: check_updated.sh
Type: application/octet-stream
Size: 692 bytes
Desc: not available
Url : http://foo-projects.org/pipermail/lunar/attachments/20070311/8cd3e2e5/check_updated.obj