Support for dependencies on different versions of the same package

[rugabarbo]

Now the tool is usable for work, because many packages are in dev status.

But let's imagine the following situation after the packages are released:

1. Package A requires version ^2.0 of package X.
2. Package B requires version ^1.7 of package X.
3. Package C requires dev-master of package X.

But the tool only installs one version of the X package and creates symlinks for one version. Manual version control with so many repositories can be very tedious...

I currently have no solutions for this problem. But we need to think about this beforehand.

[samdark]

I don't have a problem with that changing 3-4 repositories to a certain branch and then when done executing ./yii-dev exec "git checkout -- . & git checkout master".

[samdark]

How do you see ideal workflow in you case?

[rugabarbo]

How do you see idel workflow in you case?

Ideal workflow:

0. I want to work on package yii-zzz.
1. I call command ./yii-dev package/sync-dependencies yii-zzz
2. The command pulls concrete versions for the dependencies.
3. I am working with the actual versions that package yii-zzz depends on.

But there are also pitfalls here...

[samdark]

How would you commit/push changes in these concrete versions? How would you deal with pull requests that depend on each other?

[rugabarbo]

These are the details that need to be understood in advance. The number of packages is growing. Manual version resolving might be hell in the future.

[samdark]

There should not be too many inter-dependencies in the future.