Hi Sven,

thanks. Did not notice that I need three instead of two slashes. So no need
to explicitly convert to ZnUrl.

So for the records this is what works:


pathToPackageDirectory := 'C:\ClonedRepo\packages'.
Metacello new
  baseline: 'MyProject';
  repository: ('gitfiletree:///', pathToPackageDirectory)  ;
  load.         

Thanks
T. 

> Gesendet: Dienstag, 20. September 2016 um 20:41 Uhr
> Von: "Sven Van Caekenberghe" <s...@stfx.eu>
> An: "Pharo Development List" <pharo-dev@lists.pharo.org>
> Betreff: Re: [Pharo-dev] ZnPortNotANumber exception when loading from local 
> clone dir (following Metacello Guide)
>
> Hi Torsten,
> 
> Just for the ZnUrl part, have a look at
> 
> ZnFileUrlTests>>#testWindowsDriveNamesInFileUrl
> 
> AFAIK, your example should be written as:
> 
> ('filetree:///' , 'C:/ClonedRepo/packages') asZnUrl.
> 
> Or maybe,
> 
> (FileLocator C / 'ClonedRepo' / 'packages') asZnUrl.
> 
> Sven
> 
> > On 20 Sep 2016, at 20:30, Torsten Bergmann <asta...@gmx.de> wrote:
> > 
> > Hi,
> > 
> > according to the Metacello quide on [1] in section "Prime Metacello 
> > registry" one can write 
> > 
> > | pathToPackageDirectory |
> > "edit to match the path to your chosen package directory"
> > pathToPackageDirectory := '/opt/git/Sample/packages'.
> > Metacello new
> >  baseline: 'Sample';
> >  repository: 'filetree://', pathToPackageDirectory;
> >  load.
> > 
> > Adopting this for a Windows path I have:
> > 
> > | pathToPackageDirectory |
> > pathToPackageDirectory := 'C:\ClonedRepo\packages'.
> > Metacello new
> >  baseline: 'MyProject';
> >  repository: 'filetree://', pathToPackageDirectory;
> >  load.
> > 
> > But I get a ZnPortNotANumber exception, even when I use a diffent protocol 
> > like "client://".
> > Tried this in Pharo 6.0 Latest update: #60233
> > 
> > What I want to do (on Windows) is to load all project packages from a local 
> > cloned git 
> > directory (not a remote GitHub) using the dependencies given in the 
> > Baseline.
> > 
> > Did I miss something, is it just broken or the docu not up to date? If so 
> > is this a parsing issue on the Zinc URLs 
> > or an issue of Metacello API?
> > 
> > Thanks
> > T.
> > 
> > [1]  
> > https://github.com/dalehenrich/metacello-work/blob/master/docs/GettingStartedWithGitHub.md
> > 
> 
> 
> 

Reply via email to