Version Control using PVCS

[ch@SVDO]

Hi,
I'm trying to establish a version management of the packages within our EA model with PVCS.
Within our ea repository ( a single .eap file) there are two root nodes, representing the current and the to-be version of our tool suite, which is composed of different applications. The project structure looks like the following:

-Version1.x (root node)
---Tool1
---Tool2
------Class Model
------Use Case Model
---Tool3

-Version2.x (root node)
---Tool1
---Tool2
---Tool3

For connecting to PVCS I created two version control configurations pointing to two different PVCS-project on the server and two different working folders on my local file system.
One of these configurations I then applied to all the tool packages within the root node "Version 1.x" and the other configuration I applied to all tool packages within "Version 2.x".
If I then check-out a tool-package, e.g package Tool2 of root node Version1.x, then EA correctly exports it to the corresponding local working folder managed by PVCS. So far so good.    

But if I close the project and open it again, a PVCS dialog appears, asking me to specify a particular PVCS-project for the model. Why does PVCS require this? I did already specify this in the two version control settings.

Is there a limitation of one version control configuration per EA model?

thanks,
Charly