[Seaside-dev] Re: [Pharo-users] Seaside not installing

[Esteban A. Maringolo]

Hi there, please read below,

2016-09-13 9:33 GMT-03:00 Philippe Marschall <philippe.marschall at gmail.com>:
> On Tue, Sep 13, 2016 at 8:04 AM, Esteban A. Maringolo
> <emaringolo at gmail.com> wrote:

>>> Not really excited about the fix. Loading Cryptography instead of
>>> Cryptography-Pharo into Pharo causes a  issues like undeclareds and
>>> dirty system packages.
>>
>> I didn't notice that, sorry. You're right.

The Cryptography package for Pharo was a mess, overriding system
classes, methods and hence dirtying packages.
I created a new package specific for Pharo (5.0) based on the latest
from SqueakSource, and commited it in SmalltalkHub.


So... I made some changes to the config and I think I know what
caused the errors...

To start with baseline320security: was defining a group named "Tests",
which I think was a misnomer considering how other special group of
packages were named, so I renamed it to "Security Tests".

So loading "Tests" was loading Seaside-Security-Tests, which failed...

>> I could configure it and make it load arranging the spec definitions
>> in a different order, but ended up duplicating some specs for #pharo
>> and #squeak. I'll test it in a clean image to see if it works.
>
> That's probably the easiest way.

Now baseline320security: uses SmalltalkHub for the Cryptography in
Pharo and SqueakSource for Squeak.

Also, in Seaside-Core-pmm.875 the  WAKeyGenerator class>>current: was
removed (probably because it had no users if the Seaside-Security
package wasn't installed), so whenever you installed Seaside-Security
it tried to initialize a secure generator defining a secure singleton
for WAKeyGenerator and it failed.

So I commited a new version that puts the accessor back, and also made
the change in Seaside-Core-EstebanMaringolo.870 that affects the
current stable version.

Name: Seaside-Core-EstebanMaringolo.881
Ancestors: Seaside-Core-pmm.880, Seaside-Core-EstebanMaringolo.870

I loaded both #bleedingEdge and #stable in a clean image and the
Seaside-Security are green for both branches, and al tests remain
green in the #stable version.

I hope this doesn't break anything else.

Best Regards,

Esteban A. Maringolo