Why #fetch: cannot work behind a proxy? I didn't understand when he said "I can, however, download packages using the Browser" which browser? firefox or monticello browser?
Why you #fetch: cannot go behind proxy if the proxy settings are defined in the image? There was a bug with Pharo 1.3 about this but it was fixed in latest version. Which pharo version are you using? did you try to specify proxy settings? cheers On Wed, Jul 20, 2011 at 7:52 PM, Dale Henrichs <[email protected]> wrote: > Joachim, > > You are on the right track with using fetch in an image that is outside the > firewall ... zip up the directory of mcz files and you are off to the races. > > BTW, you don't need an "empty" image if you set ignoreImage to true before > doing the fetch: > > version ignoreImage: true. > > Dale > > > ----- Original Message ----- > | From: "jtuchel" <[email protected]> > | To: [email protected] > | Cc: "A friendly place where any question about pharo is welcome" < > [email protected]> > | Sent: Wednesday, July 20, 2011 10:44:46 AM > | Subject: [Metacello] Aw: Re: [Pharo-users] Using SqueakSource / Metacello > "offline" > | > | Hi Norbert, > | > | > | thank you for the links. > | > | > | One question remains unanswered: is there a way to determine which > | .mcz files are needed without using #fetch (because fetch doesn't > | work behind the proxy)? I guess the answer is no, because I have no > | way of looking into the required Configurations that are unfetched. > | So I need to use a local directory and try step by step and download > | the mcz that is currently missing... oh my. > | > | > | Or can I use a fresh image on a machine in another network to fetch > | all and copy the contents of my package cache onto the target > | machine??? > | > | > | Joachim > -- Mariano http://marianopeck.wordpress.com
