Should SUnit be part of Basic? (was Re: Against package removal
before packages work correctly)
Doug Way
dway at riskmetrics.com
Sun Jun 29 20:22:46 UTC 2003
Anthony's post brings up something I was thinking about recently...
Should SUnit be part of the Basic configuration?
The Basic configuration is the platform containing all the essential
development tools, I believe. The IDE, basically. We haven't really
strictly defined this, but this is what the original idea was. (Side
note: I don't think there's a swiki page or anything covering what
Full/Basic/Minimal are... we should write this down somewhere.)
Is SUnit an essential development tool? I would say yes... we are
trying to encourage folks to include tests with fixes, and requiring
test packages for Squeak-official packages.
If we decide that SUnit should be part of Basic, this also means that
we should add it back into the update stream now, since we decided to
move toward Basic before we start continuing to Minimal. I think this
is probably a good idea anyway as a matter of convenience until SM 1.1
and dependencies are ready. (This is the only removed package that I
think might belong in Basic... the others (Balloon3D, VMMaker, etc.)
should probably stay out.)
Thoughts?
- Doug
On Saturday, June 28, 2003, at 09:21 PM, Anthony Hannan wrote:
> I just tried to install SmaCC-Development from SqueakMap into a fresh
> 3.6 image and I got an error because SmaCC tries to add a method to
> TestCase which no longer exists in 3.6.
>
> Why are we removing packages before the package infrastructure is
> completely implemented (including dependents)? It doesn't make sense.
>
> Cheers,
> Anthony
More information about the Squeak-dev
mailing list
|