[Pharo-users] #pathString: sent to nil when loading with Metacello

Tim Mackinnon tim at testit.works
Mon Feb 11 06:22:12 EST 2019

I will log this as a bug - unless someone has any other thoughts. It looks to me that Iceberg incorrectly ignores the full path of a repository, meaning that other projects could equally collide with each other by virtue of having the same name? (e.g. #guessRegisteredRepository is guessing wrong0


> On 8 Feb 2019, at 10:28, Tim Mackinnon <tim at testit.works> wrote:
> Hi - I’m trying to pick up the Exercism project again - and when trying to come up with instructions for students to load a clean image from the command line (to fit in with their expectations from other tracks and show that Pharo is also capable of great command line foo) I get the error:
> #pathString: was sent to nil - when I do:
> ./pharo-ui Pharo.image eval "
> Metacello new 
>  baseline: 'Exercism'; 
>  repository: 'github://exercism/pharo:master/dev/src <github://exercism/pharo:master/dev/src>';
>  load."
> Ben Coman mentioned to me that this has something to do with the "pharo-project/pharo" repository being pre-defined in Pharo 7? 
> What does this mean? The repo //exercism/pharo was given to us by the Exercism team to match repo’s of other languages like //exercism/ruby etc.
> So is this really what the problem is - we can’t have a repo that includes the name pharo - or have I misunderstood this? Is there a workaround I can put in the do-it to bypass this somehow?
> I’m hoping we might have a good answer, as it was going so well in Pharo 6.
> Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20190211/70329c4a/attachment.html>

More information about the Pharo-users mailing list