[Mellroth]

Hi,

as I remember, the older versions of VIPM had an option to store dependencies in the vip-file itself (but differently name-spaced).
Is this at all possible with the current version?

/J

[Michael Aivaliotis]

Yes. By default, if you don't explicitly define external dependancies, they are stored inside the VIP file.

[Mellroth]

Michael Aivaliotis, on 23 December 2011 - 02:14 AM, said:

Yes. By default, if you don't explicitly define external dependancies, they are stored inside the VIP file.

This is normally true for folders outside of the .vipb folder, but does not work for dependencies in user.lib etc.
And, as far as I can tell the automatically added dependencies are not renamed.

What I want to do is to create a simple vip that doesn't install other packages (like the vipc file), but contains all dependencies but renamed to avoid name collisions.

The reason behind this is to make sure my Package A that is using Package C in version 1.0.0 is not affected when I install Package B that is using Package C in version 2.0.0, i.e. I want to be able to have the used portions of Package C in different versions loaded at the same time.

/J

[Michael Aivaliotis]

Mellroth. I realize this is an old thread. But wanted to follow up and make sure I'm understanding your specific problem. We are making some fixes to the next release of VIPM and I want to make sure that your issue is not a bug. Are you running VIPM PRO?