Hi Pierce,
I did actually use the following expression:
Metacello new
githubUser: 'DuneSt' project: 'ChartJs' commitish: 'master' path: 'src';
baseline: 'ChartJs';
onUpgrade: [ :e | e useIncoming ];
onConflictUseLoaded;
onWarningLog;
load.
Thinking about it, maybe the #onUpgrade: and #onConflictUseLoaded can't used
together, I don't know.
I normally load Seaside3 as a dependency to Bootstrap:
spec baseline: 'Bootstrap' with: [ spec repository:
'github://astares/Seaside-Bootstrap:master/src' ].
which loads Seaside as:
seaside3: spec
spec
baseline: 'Seaside3'
with: [ spec
loads: #('default' 'REST');
repository: 'github://SeasideSt/Seaside:master/repository' ]
while ChartJS uses:
seaside3: spec
spec baseline: 'Seaside3' with: [ spec repository:
'github://SeasideSt/Seaside:v3.4.x/repository' ]
Maybe the differences in URL (the version tag) and maybe also the groups make
them incompatible/different ?
Sven
> On 12 Feb 2020, at 01:10, Pierce Ng <pie...@samadhiweb.com> wrote:
>
> On Tue, Feb 11, 2020 at 05:06:44PM +0100, Sven Van Caekenberghe wrote:
>> NeoJSON and Seaside are already in my project's dependencies, but
>> Seaside3 seems to never resolve to the same thing, so I would like to
>> skip that. Is that possible ? I have this issue often with Seaside. I
>> could fork and edit the baseline, but I'd rather not.
>
> I do the following near the top of my load script:
>
> Metacello new
> baseline: 'Seaside3';
> repository: '...';
> load;
> lock.
>
> And when loading other packages that may want to load another version of
> Seaside:
>
> Metacello new
> baseline: 'whatever';
> repository: '...';
> onConflictUseLoaded;
> load.
>
> I tried doing ifTrue:ifFalse: conditional loading in my baseline to test
> for Seaside, but it didn't work.
>
> Pierce
>
>
