[plt-scheme] reporting on planet packages and versions used by a set of collections & other tools

On Mon, Sep 1, 2008 at 2:07 PM, Neil Van Dyke <neil at neilvandyke.org> wrote:
> Agreed, *should*.  You know I'm going to play devil's advocate here. :)
>  Rarely do we actually prove that given changes are backward-compatible wrt
> a specification, and even more rarely do we prove that all the interactions
> among units rely only on specified behavior.  By "rarely," I mean "never,"
> for virtually everyone, including myself.

Agreed.

> Just within my own systems, I'd like to know whether my assertions of
> version compatibility are correct.  Testing unit version combinations within
> my systems can inform me of reliance on unspecified behavior or of a
> non-backward-compatible change that was not caught in unit testing with the
> versions I happened to be using.  Ideally, I would be informed before I
> submitted code to PLaneT that falsely claimed to be backward-compatible or
> that had overly liberal "require"'d versions.

I've done some reading of the Planet API and it looks like all the
information is available, but the functions are not conveniently
presented.  Note that util.ss in the planet collection exports more
bindings than are documented.

N.