Thanks Sven. I fixed it.
Now you should be able to do

Gofer new
������ squeaksource: 'MetacelloRepository';
������ package: 'ConfigurationOfGlorpDBX';
������ load.

ConfigurationOfGlorpDBX project latestVersion load: 'GlorpPostgresV2NativeWithTests'.

And everything should be fine.

Thanks

On Tue, Nov 8, 2011 at 6:17 AM, Sven Van Caekenberghe <sven@beta9.be> wrote:
Hi,

As I wrote some time ago:

On 24 Oct 2011, at 09:38, Sven Van Caekenberghe wrote:

> A couple of days ago I got it working in 1.3 with the native (non-dbx) postgresql driver.
>
> I basically did:
>
> Gofer new
> � � � squeaksource: 'MetacelloRepository';
> � � � package: 'ConfigurationOfGlorpDBX';
> � � � load.
>
> ConfigurationOfGlorpDBX project latestVersion load: 'GlorpPostgresV2NativeWithTests'.
>
> I can't remember exactly, but it more or less worked out of the box.
>
> I did some patches for timestamp decoding and blobs, but these won't hit you right away.

For the patches, see my two other mails of today.

I do also have an issue with ConfigurationOfPostgresV2: it depends on Cryptography, but that is unneccesary on Pharo as I think the only thing needed is MD5 encoding which Pharo has out of the box. (Cryptography is way too big).

I can't seem to figure out where this config actually came from (it says local package cache in my image), ConfigurationOfGlorpDBX>>#baseline22: says

� � � � � � � �spec package: 'GlorpDriverPostgreSQL' with: [
� � � � � � � � � � � �spec repository: 'http://www.squeaksource.com/PostgresV2'.
� � � � � � � � � � � �spec postLoadDoIt: #postLoadGlorpPostgresNativeDriverDBXTalkPharo.
� � � � � � � � � � � �spec requires: #('PostgresV2' 'Glorp' ) ].

But I can't find it in http://www.squeaksource.com/PostgresV2 either ;-)

Anyway, could someone please help to patch ConfigurationOfPostgresV2 to not load Cryptography on Pharo ?

Thx,

Sven







--
Mariano
http://marianopeck.wordpress.com