Once and only once - code that affects packages should be distributed in no other way than by being in the package.
This important for two reasons - 1. The package owner really should be the only one that decides about code that goes in his package. 2. If packages depend on active Harvesting of all their stuff, that slows down the maintainance of base itself, and the evolution of all packages. The opposite of what we want.
Part of this is removing concerns from the Harvesters. The maximum they should worry about packages is that when packages are updated that affect a certain image brand (base, full), the maintainer of the image should have the option of making the package update itself. Of course, this can be done easily if SM in the image, which is not a problem for Base and Full.
Daniel
John M McIntosh johnmci@smalltalkconsulting.com wrote:
On Thursday, May 8, 2003, at 04:22 AM, goran.hultgren@bluefish.se wrote:
But the update stream is only used for code not in packages. It can only "expect" an image that doesn't have SM. Aargh. My head spins.
Need to think more...
Well any way to change the update stream logic to consider packages. Then the update stream could update packages if they are installed, otherwise they get skipped. Later if you load said package and rerun the update, it might go back and re-apply updates as needed based on which packages are now loaded?
--
=== John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
Squeakfoundation mailing list Squeakfoundation@lists.squeakfoundation.org http://lists.squeakfoundation.org/listinfo/squeakfoundation