Skip to content
This repository has been archived by the owner on May 31, 2018. It is now read-only.
This repository has been archived by the owner on May 31, 2018. It is now read-only.

improve cyclic dependency error message output #739

Open
@rmarquis

Description

Cyclic dependencies are correctly detected (see f.e. #734), but knowing which target is responsible for it isn't straightforward.

:: Package pdftk not found in repositories, trying AUR...                                                                                
:: resolving dependencies...                                                                                                             
tsort: -: input contains a loop:                                                                                                         
tsort: gcc-gcj-ecj                                                                                                                       
tsort: gcc63-gcj                                                                                                                         
tsort: gcc63                                                                                                                             
tsort: -: input contains a loop:                                                                                                         
tsort: gcc-gcj-ecj                                                                                                                       
tsort: gcc63-gcj                                                                                                                         
:: dependency cycle detected 

This isn't an issue when explictly installing a specific package, but can be when updating as it might be difficult to know which target is responsible for the issue. Modify the error message to display the target, similarly as done in #173.

:: dependency cycle detected (target -> dep1 -> dep2 -> dep1)

This might not be straightforward to do with tsort, but might be easier done in conjunction with the solver provided by auracle (see #720).

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions