El mar, 04-08-2009 a las 11:00 -0700, Chris Cunningham escribió:
Have you given any thought to how you want the publicly consumable version of Pharo named? As I understand it, the PharoCore is for the Pharo development teams consumption; there is another version that is intended for the end user. Is this correct? If so, a simpler naming scheme might be nice there.
This is currently managed by Damien Cassou and Torsten Bergman. They generate the public consumption images for unix/mac/windows. I think that as the public ones are derived from the core image, a simplification of the pharo core (that was generated from by adding packages and a nice one-click setup) name could be useful. Pharo-X.Y-#####.zip without the tagname. For example: for unix/mac/image Pharo-0.1-10402.zip for the win32 Pharo-0.1-10402.exe for the 1.0 release: Pharo-1.0-RELEASE_1_0.zip Pharo-1.0-RELEASE_1_0.zip and for the updates: Pharo-1.0-UPDATE_1.zip Pharo-1.0-UPDATE_2.zip Pharo-1.0-UPDATE_1.exe Pharo-1.0-UPDATE_1.exe Or something like that. Keep in mind that the images for public consumption add other packages that might have their own updates/fixes/patches so the names need to consider this too when an update or fix affects a package but no the core image. But this is in the end a decision of the packagers. They may have a better arguments for ther current name formats. Cheers, Miguel Cobá
Also, is there a desire to create a new sources file for the 1.0 release? Or at least changing the name from Squeak39.sources to something like Pharo1.sources? Not critical, but could reduce some confusion.
I'd ask the same thing about the VM name, but I suspect that wouldn't be the best choice - leaving it with the Squeak name on it guides the user to the conclusion that they might be able to grab any SqueakVM that have a chance that it will work with Pharo. And they'd probably be right, if it is a new enough VM.
This was all triggered by installing the Beta release last night and noticing the various names floating around, and then seeing this discussion.
-Chris _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project