be a "package" of its own (ie, have its own PackageInfo namespace).
I wouldn't mind having the repository be able to store arbitrary associated files with each package; this could also be used to attach changesets. Not really sure what the interface to this would be though. And there are other things that are higher priority (like branching).
Ideally, of course, the packages would all be in the repository, and an ENH would just be a branch.
Avi
squeakfoundation@lists.squeakfoundation.org