Library and runtime dependancies cause incorrect circular dependancies

[danchr@…]

Summary:

If you create two ports, A and B, and A has a library dependancy on B and B a runtime dependancy on A, installing A should result in first A, then B being built, installed and activated. However, DP does not seem to distinguish between the various kinds of dependancies, and will refuse to install port A.

Steps to reproduce:

1. Download and decompress the attached portfiles.
2. Put them in a repository DP will know about and update the index the repository.
3. 'port install gift'

Expected results: First gift is installed, and then it's four runtime dependancies are installed.

Actual results: DP tries to install them all at once, which it can't, and thus bails out.

[markd@…]

(In reply to comment #0)

If you create two ports, A and B, and A has a library dependancy on B and B a runtime dependancy on A, installing A should result in first A, then B being built, installed and activated. However, DP does not seem to distinguish between the various kinds of dependancies, and will refuse to install port A.

Steps to reproduce:

1. Download and decompress the attached portfiles.

Is this problem still relevant? There are not portfiles attached either.