On 2013-05-22, at 15:22, Goubier Thierry <[email protected]> wrote:
> Le 22/05/2013 15:12, Camillo Bruni a écrit : >> >> On 2013-05-22, at 15:05, Camillo Bruni <[email protected]> wrote: >> >>>>>> Not sure I can answer that; in the meantime, I just added a FileTreeUrl >>>>>> as a >>>>>> subclass of FileUrl, and Gofer seems happy with that. >>>>> >>>>> Neat. >>>> >>>> Now, I can do: >>>> >>>> ./pharo Pharo.image eval --save Gofer new url: >>>> \'filetree://`pwd`/../../src\'\; package: \'TauC-Parser\'\; load >>> >>> cool! >>> >>>> And a long time after (package loading is slowwww), it's done. >>>> >>>> However, the --install in the config handler doesn't work; had to use >>>> --install=stable instead. >>> >>> that's in 2.0 I guess, since I changed it to use #stable by default in 2.0. >>> So we should push the FileTreeUrl into the 2.0 repository for FileTree.. >> >> or simpler, change the command line handler to use GenericURL > > Well, with FileTreeUrl, if you have a config in your filetree repo, you can > use config filetree:///whatever ConfigurationOf; no need to change the > ConfigurationCommandLineHandler for that. > > I haven't done a ConfigurationOf for that project, so I wanted to load > packages by packages (hence the eval) but you'll notice this is almost the > same code as ConfigurationCommandLineHandler. yes, I came to the same conclusion: https://github.com/dalehenrich/filetree/issues/74 :)
