I think we're already there in trunk, but I've been busy lately with a job
hunt, and presently haven't got a working VM to check. I think the thing to
do is get a recent trunk image, update it, and look at what's in the package
"Configurations"

On Thu, Jul 8, 2010 at 8:13 PM, Rob Withers <reefedjib at yahoo.com> wrote:

>  Casey,
>
> This works for me.  As long as Crypto is visible and easily loadable I
> think the requirements are met.  Any idea when this "community supported
> packages" will become a reality?
>
> Cheers,
> Rob
>
>
>  *From:* Casey Ransberger <casey.obrien.r at gmail.com>
> *Sent:* Thursday, July 08, 2010 10:11 PM
> *To:* The general-purpose Squeak developers list<squeak-dev at lists.squeakfoundation.org>
> *Subject:* Re: [squeak-dev] Re: [Vm-dev] Cryptography in the main image
> and Plugins build for theVMs
>
> There is a plan that solves this problem using Monticello configurations.
> We're calling them community supported packages. More info here:
>
> http://comments.gmane.org/gmane.comp.lang.smalltalk.squeak.general/148414
>
> <http://comments.gmane.org/gmane.comp.lang.smalltalk.squeak.general/148414>Basically,
> you can keep your bits shipping as automatically loadable from Squeak where
> version and dependency information is preserved. It's pretty sweet:)
>
> On Thu, Jul 8, 2010 at 7:00 PM, Rob Withers <reefedjib at yahoo.com> wrote:
>
>>
>> --------------------------------------------------
>> From: "Steve Wart" <steve at wart.ca>
>> Sent: Thursday, July 08, 2010 7:50 PM
>> To: "Squeak Virtual Machine Development Discussion" <
>> vm-dev at lists.squeakfoundation.org>
>> Cc: "Squeak Crypto" <cryptography at lists.squeakfoundation.org>; "Squeak
>> Dev" <squeak-dev at lists.squeakfoundation.org>
>> Subject: Re: [Vm-dev] Cryptography in the main image and Plugins build for
>> theVMs
>>
>>
>>
>>> Given that cryptography still faces export restrictions, would this
>>> cause problems for OSS distributions that want to include Squeak?
>>>
>>>
>> I am not familiar with which pieces of Cryptography are export restricted
>> and which are not.   According to the Java SDK Crypto docs (
>> http://download.oracle.com/docs/cd/E17476_01/javase/1.4.2/docs/guide/security/CryptoSpec.html#Architecture)
>> DSA, MD5 and SHA-1 are at least distributable.  This obviously reduces the
>> attractiveness of including Crypto in the image, were we to have to split
>> the package into exportable and non-exportable packages.
>>
>>
>> Also I'm not sure that people who want to minimize their image size
>>> would benefit. Why can't Cryptography be easily loaded by people who
>>> need it?
>>>
>>
>> People may not know where it resides.  It is not a part of the trunk.  It
>> is in a SqueakSource repository.
>>
>> Thanks,
>> Rob
>>
>>
>>
>>> Steve
>>>
>>> On Thu, Jul 8, 2010 at 2:07 AM, Rob Withers <reefedjib at yahoo.com> wrote:
>>>
>>>>
>>>> Hi all,
>>>>
>>>> I would like to propose that Cryptography be included as part of the
>>>> image,
>>>> by default.  As it stands now it is in the Cryptography repository,
>>>> which
>>>> most don't seem to know about or there are one-off copies that are
>>>> developed
>>>> separately.  David Shaffer has been stewarding a reintegration of these
>>>> forks and ensuring the tests pass.  Everyone should be able to take
>>>> advantage of the algorithms provided by the Cryptography package.
>>>>
>>>> Along the same lines, it would be a great help for the vm providers to
>>>> include the CryptographyPlugins when they build a new vm.  I believe
>>>> there
>>>> are 3 plugins and they really ought to be build internally, since they
>>>> are
>>>> unchanging.
>>>>
>>>> I would like to hear what others think of the possibility of making this
>>>> change.
>>>>
>>>> Thank you,
>>>> Rob
>>>>
>>>>
>>>>
>>>>
>>
>
>
> --
> Casey Ransberger
>
> ------------------------------
>
>
>
>
>
>


-- 
Casey Ransberger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20100708/8bb51e1b/attachment.htm