The error you hit was because the package loader was smart enough to notice
that there was a version conflict between the version of a subproject
already in the image and what the new load instructions were telling it to
load. The title of the debugger you pasted in alludes to that fact.
So what you need to do is decide what to do when there is a conflict as its
tricky for a package manager to figure out what it should do in every case.
Metacello includes an instruction #onConflict: which accepts a block. You
can write code in the block to decide wether to use the incoming version or
the extant version in the image or whatever. e.g.
Metacello new
repository: 'github://PierceNg/glorp-sqlite3:pharo7';
baseline: 'GlorpSQLite';
onConflict:[:ex | ex allow];
load.
would likely get everything to load without issue. Then you'd have to run
the tests to see if the version conflict caused problems.
Pharo Smalltalk Users mailing list wrote
> Nice! Thanks.
>
> So here is maybe a stupid question (and I'm gonna read the wiki stuff on
> packages next) but it seems to me that the package loader should notice
> that glorp is already loaded and not load it if glorp is specified as a
> prerequisite but instead it fails.
>
> Is the package loader not smart enough to understand what is already
> loaded and skip load attempts?
>
> Puzzling.
>
>> On Oct 19, 2019, at 11:23 PM, Pierce Ng <
> pierce@
> > wrote:
>>
>> On Sat, Oct 19, 2019 at 01:26:10AM -0700, Todd Blanchard via Pharo-users
>> wrote:
>>> I loaded GLORP+P3 without issue.
>>> Trying to load SQLite3 - it also wants to load GLORP which complains of
>>> conflict.
>>
>> Todd, to load SQLite3 only:
>>
>> Metacello new
>> repository: 'github://astares/Pharo-UDBC/src';
>> baseline: 'UDBC';
>> load: 'SQLite'
>>
>> Pierce
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
