[Pharo-project] ConfigurationOfPharoVM

Dale Henrichs dhenrich at vmware.com
Sat Jul 7 23:08:38 EDT 2012


Keep in mind the fact that if you chain baselines or versions in this way, it is very difficult for humans to understand just what they are getting.

It also makes it harder for tools to do the right thing as well ...

So I recommend against chaining...

Dale

----- Original Message -----
| From: "Mariano Martinez Peck" <marianopeck at gmail.com>
| To: Pharo-project at lists.gforge.inria.fr
| Sent: Saturday, July 7, 2012 3:28:22 PM
| Subject: Re: [Pharo-project] ConfigurationOfPharoVM
| 
| 
| 
| 
| On Sat, Jul 7, 2012 at 9:03 PM, Sean P. DeNigris <
| sean at clipperadams.com > wrote:
| 
| 
| I noticed the versions vary between x.x.x and x.x-x and that some of
| the
| versions import baselines and others import other versions. I've
| never seen
| it done like that... what's the intention?
| 
| 
| 
| Usually, a version imports a baseline. However, imagine that you have
| several packages/projects and between version X and Y only changed a
| few packages.
| Instead of having to re-put all versions of all packages in Y, you
| make Y import X and you just change the ones you want.
| 
| 
| 
| e.g.
| "Baseline with dot imported by version with dash"
| version145: spec
| <version: '1.4-5' imports: #('1.4.1-baseline')>
| 
| "version importing another version"
| version143: spec
| <version: '1.4-3' imports: #('1.4-2')>
| 
| Cheers,
| Sean
| 
| --
| View this message in context:
| http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html
| Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
| 
| 
| 
| 
| --
| Mariano
| http://marianopeck.wordpress.com
| 
| 




More information about the Pharo-dev mailing list