[squeak-dev] Crypto package loading?
asqueaker at gmail.com
Sat Oct 27 02:13:05 UTC 2012
Just a reminder here are the instructions for publishing on SqueakMap.
I intend to publish new versions of all of my projects once 4.4 is
released. If we all will do that a nice list of external loadable
packages accumulates for Squeak 4.4. I'll help if anyone has trouble
On Fri, Oct 26, 2012 at 6:10 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Fri, Oct 26, 2012 at 11:28:09PM +0100, Frank Shearar wrote:
>> On 26 October 2012 19:48, Chris Muller <asqueaker at gmail.com> wrote:
>> >> ok. who could put this into the Extending the system workspace?
>> > Guys, do we agree that, until we have a replacement, SqueakMap should
>> > be the "App Store" for Squeak?
>> > Extending the System workspace is going away. No one should be doing
>> > any work there other than removing it.
>> It's a chunk of text telling people how to load things. While I agree
>> that SqueakMap ought to be the place to go, it isn't right at the
>> moment. However, I'd be happy to regard that (pushing SM, getting it
>> properly on track etc) as being a core part of 4.5.
> SqueakMap is not something to be done some time in the indefinite future.
> It has been around a long time, and we just need to *use* it.
> If a package is important enough to put on SqueakMap, then just do it. It
> won't get any easier by waiting until Squeak 4.5. And if it is not important
> enough to be worth the trouble of listing it on SqueakMap, then it's probably
> not very important and there would be little point in putting it into the
> extending the system workspace or adding it to the image.
> Chris is giving good advice here. If the rest of us make an effort to help
> out by registering important packages on SqueakMap it will help all of us,
> and nobody will need to worry about lobbying to get their favorite package
> included in the image.
>> >>>> On a side note, what is the status of Crypto going
>> >>>> into trunk?
>> > Since so many types of apps do not need any cryptography, I think it
>> > should remain a separately loadable package.
>> Agreed. Strip more stuff out the image, and make it much easier to
>> load packages.
More information about the Squeak-dev