Bert Freudenberg wrote:
> 
> However, it's *entirely* possible to provide your own PackageInfo
> subclass that uses different means of retrieving the list of classes.
> Like, simply by storing an explicit list.

Interesting. How do you avoid a tug-of-war over
which package "owns" a class. If the shared class
is in a package which uses the class category to
determine its classes, and another package (through
its PackageInfo) also assert ownership of that
shared class, then both packages with save it
out. When loading, the last one to load will
overwrite the first one. When first saved out,
the classes would be identical, but if they then
take different development streams, then there's
going to be a problem at some point.

-- 
Yanni Chiu