We are always happy to reconsider any of our policies. What we are dealing with here is both a licensing issue and a technical issue.
First the technical issue: The development tools were not designed with the intent of being packaged. So, for example, they are not terribly rigorous about declaring prereqs and they are not well-factored for subdividing into smaller apps.
Then the licensing issue: It is not clear how to divide the code in the development apps into OK for runtime and not OK for runtime.
The only time I can think of that we have dealt with this issue in the past is when we enabled the Compiler for packaging (due to a customer desire to be able to have their end-users program their business app in a subset of Smalltalk). So, tell us what part of the development tools you specifically want at runtime and I'll tell you if it's possible.
John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.