[Pharo-project] Managing images: new files vs. new folder
Hello all, How do you handle a new version of Pharo? Obvious choices are to unzip in the same directory with the previous image, and to create an image-specific directory. I have succesfully put various images in one folder in the past, but I worry about MC stepping on itself in the then common package cache. There are some advantages to that approach, but if MC gets into trouble, it's a bad idea. Bill
Bill, Monticello shouldn't have a problem sharing the package cache, although concurrent access in the package cache directory could be problematic, but you'd have to be in the middle of downloading a package into the cache in one image while accessing the package from the cache in another image... Dale ----- "Wilhelm K Schwab" <bschwab@anest.ufl.edu> wrote: | Hello all, | | How do you handle a new version of Pharo? Obvious choices are to | unzip in the same directory with the previous image, and to create an | image-specific directory. I have succesfully put various images in | one folder in the past, but I worry about MC stepping on itself in the | then common package cache. There are some advantages to that | approach, but if MC gets into trouble, it's a bad idea. | | Bill | | | | _______________________________________________ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Dale, I ask because creating a new directory adds a couple of small wrinkles. First, it generally requires that I update my file transfer/backup configuration, or at least fiddle with it more than would be necessary if several images live in the same directory. It also forces me to mess with (thinking Linux here) menu configuration; if images share a common directory, I can simply edit a common shell script to load the new image, and the main menu is blissfully unaware of it. In the transition period, or to run an older image, I will copy/paste into a terminal, but I am too lazy<g> to do that for my "current" image under ordinary conditions. If anybody thinks they have the ultimate answer (or horror stories about doing the wrong thing), I'd like know about it. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Dale Henrichs Sent: Saturday, November 21, 2009 3:16 PM To: Pharo-project@lists.gforge.inria.fr Cc: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Managing images: new files vs. new folder Bill, Monticello shouldn't have a problem sharing the package cache, although concurrent access in the package cache directory could be problematic, but you'd have to be in the middle of downloading a package into the cache in one image while accessing the package from the cache in another image... Dale ----- "Wilhelm K Schwab" <bschwab@anest.ufl.edu> wrote: | Hello all, | | How do you handle a new version of Pharo? Obvious choices are to | unzip in the same directory with the previous image, and to create an | image-specific directory. I have succesfully put various images in | one folder in the past, but I worry about MC stepping on itself in the | then common package cache. There are some advantages to that | approach, but if MC gets into trouble, it's a bad idea. | | Bill | | | | _______________________________________________ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (2)
-
Dale Henrichs -
Schwab,Wilhelm K