#pathString: sent to nil when loading with Metacello
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'; 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
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 Tim
On 8 Feb 2019, at 10:28, Tim Mackinnon <tim@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
participants (1)
-
Tim Mackinnon