Regarding sharing a package cache, I made a change a while ago that
searches up the directory tree to see if there is one higher up. You
then don't have to change the fresh image. What do you think?

Cheers
mike

On Tuesday, April 20, 2010, Stéphane Ducasse <[email protected]> wrote:
>
> On Apr 20, 2010, at 1:00 AM, Sean P. DeNigris wrote:
>
>>
>> http://code.google.com/p/pharo/issues/detail?id=2329
>>
>> Pharo image: Pharo 1.0
>>
>> In Monticello Browser, when I click "+Repository" and select "directory,"
>> I'd love to be taken right to the directory where I keep my local
>> repositories, instead of having to click to the same place over and over.
>>
>> I changed the following method:
>> MCDirectoryRepository class>>morphicConfigure
>>       ^ (UIManager default chooseDirectoryFrom: (FileDirectory on:
>> '/path/to/my/Repositories')) ifNotNil:
>>               [:directory |
>>               self new directory: directory]
>>
>> How should I store the default repository directory?  Would anyone else find
>> this helpful?
>
> it would be good to be able to
>         either choose to have one local cache on the side of the image
>         or one shared among image - this implies a way to store and set it up
>                 => probably a class variable + a setting in 1.1
>>
>> Sean DeNigris
>> --
>> View this message in context: 
>> http://n4.nabble.com/FEATURE-User-chooses-preferred-location-for-MC-directory-repositories-tp2016684p2016684.html
>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to