Version generated from a baseline can have empty package versions in a platform-specific section

A version method generated from a baseline that mentions a package in both the 
#common and some platform-specific sections, will end-up with an empty package 
version in the platform-specific section of that version method.
This means that the most recent version of the package will get loaded for that 
platform, rather than the specific version mentioned in the common section. 
This leads to errors. The manual solution is to remove the statement from the 
platform-specific section of the generated method.

A baseline along the lines of:

baseline100: spec
   spec for: #common do:[
        spec package: 'A' ]

   spec for: #pharo do:[
         spec package: 'A' with:[ spec requires: #(Project) ] 
    ]

Will thus generate a version method like:

version103: spec 
   spec for: #common do:[
        spec package: 'A' with: 'A-Johan.1 ]

   spec for: #pharo do:[
         spec package: 'A' with: ''] 
    ]

Original issue reported on code.google.com by jo...@yesplan.be on 1 Sep 2012 at 2:53

Attachments:

photo.JPG

krfkeith / metacello

Version generated from a baseline can have empty package versions in a platform-specific section #181