You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Include the full path to the package for each reverse dependency and then verify whether the reverse dependency exists by looking at this path.
The current way is that reverse dependencies are removed from the database whenever a package is removed, which turns out to be rather annoyingly fragile. We should make use of our package database to verify whether a package still has a reverse dependency present in the nimble install directory.
The text was updated successfully, but these errors were encountered:
Include the full path to the package for each reverse dependency and then verify whether the reverse dependency exists by looking at this path.
The current way is that reverse dependencies are removed from the database whenever a package is removed, which turns out to be rather annoyingly fragile. We should make use of our package database to verify whether a package still has a reverse dependency present in the nimble install directory.
The text was updated successfully, but these errors were encountered: