Hi,

I have my project with my Configuration and I am using spec groups to load 
different sets of packages (e.g., development and user groups).

With the porting to Pharo 4.0 I discovered that there are some functionalities 
specific to Pharo 3.0 and others to Pharo 4.0, for example the fact that 
MethodContext is no longer part of Pharo 4.0. but it has been replaced by 
Context.

I moved such functionalities in a package, say 'MyProject-Extension30’ and 
Pharo 4.0 specific functionalities in 'MyProject-Extension40’.

Now the question is, suppose that I have a group like
spec group: ‘User' with: #(‘A’ ‘B’ ‘C’).

and another one:
spec group: ‘Dev' with: #(‘A’ ‘B’ ‘C’ ‘D’ ‘E’).

Until now, the developer (i.e., me) would do something like
(self project version: #bleedingEdge) load: #('Dev’)

and a used of my project would do
(self project version: #bleedingEdge) load: #(‘User’)



How can I factor inside the dynamic load of the two Pharo-version specific 
packages?
i.e., no matter if ‘User’ or ‘Dev’ group is loaded I need to load 
'MyProject-Extension40’ if I am on Pharo 4.0 and 'MyProject-Extension30’ if on 
Pharo 3.0.

Thanks for your help,
Roberto

Reply via email to