Comments (10)
should be resolved with the merge of #551
from hackage-server.
The main problem with dependencies is that there are just so many of them! So, the implementation allowed you to answer these questions for a given package very quickly:
/package/baz-1.0
,/package/baz/reverse/summary
- How many different packages have some version which depends directly on some version of baz?
- How many different packages have some version which depends directly on baz-1.0?
/package/baz/reverse/summary
- How many different packages have some version which depends directly or indirectly on some version of baz?
/package/baz/reverse/all
- What are the different packages which have some version which depends directly and indirectly on any version of baz, and how many direct and indirect reverse dependencies do they each have?
/package/baz-1.0/reverse
- What are the packages for which the latest version depends on baz-1.0, and what are those respective versions?
/package/baz-1.0/reverse/old
- What are the different packages for which the latest version does not depend on baz-1.0, but some older version does, and what are those respective versions?
/packages/reverse
- What are all packages which have direct reverse dependencies, sorted by the number of direct reverse dependencies, and what is the number of total (direct + indirect) reverse dependencies they have as well?
Some of the problems of the implementation:
- All flags-controlled alternatives are allowed to be true simultaneously so no dependencies are missed-out on (see getAllDependencies).
- I am certain space leaks abound.
- Because ReverseIndex is an acid-state component with frequent updates, these updates should take in as small arguments as possible to keep the logs as small as possible, which means that it is better for operations to depend on internal state rather than passed-in state.
- Consequently, non-leaked space also abounded. Updating a package in this scheme requires holding onto:
- A complete map from a depended-on package baz to the VersionRange of every version of every package with a dependency on baz. This is in case a new version baz-1.2 gets uploaded, so the list of reverse dependencies can be created for that baz-1.2 (if someone depends on baz-1.1.*, they get excluded from this list).
- A complete map from a depended-on package version baz-1.2 to every version of every package which depends on it. For example, we not only know that foo depends on baz-1.2, but foo-4.0, foo-4.1, etc. This is used for checking if the latest version of foo depends on baz-1.2, or only an older/deprecated version.
- A complete enumeration of all packages and versions, duplicating the main index. This is in case a package foo-4.4 is uploaded which depends on bar <2.0, foo-4.4 should be added as a reverse dependencies to all versions of bar <2.0 in the index. The only way to get a list of such versions is to have a list of all existing packages.
The structure is complex, but it allows somewhat complex questions to be answered. For example, which packages depend only on an older version of some package, so they can be notified to upgrade to a newer version to help mitigate binary incompatibility? This could be detected for a package candidate. Or, which packages depend on some package only in their older versions, meaning that dependencies are being dropped over time (and may not be useful for determining popularity here)?
As an out-there idea: there are conceivably other services that are just as complicated as revdeps that Hackage might want to offer, like finding similar packages using dependencies, analyzing build reports to make diagnoses, or suggesting tags. Ideally, smart clients could handle as much of these as possible, with the server only providing the UI for them. Can this be done with revdeps?
from hackage-server.
For the record: https://packdeps.haskellers.com/reverse can be used now to figure out the reverse dependencies.
from hackage-server.
That has existed for eight plus years. Its irrelevant to this ticket.
from hackage-server.
It is relevant for people like me that find this ticket as their first google hit and want the functionality now.
from hackage-server.
This ticket is not for that purpose. Its a ticket for tracking hackage issues.
from hackage-server.
is this still active ? https://packdeps.haskellers.com/reverse is great but it is missing some hackage packages
from hackage-server.
is this still active ? packdeps.haskellers.com/reverse is great but it is missing some hackage packages
Also, it ignores dependencies under flags (and maybe also conditionals, testsuites?).
from hackage-server.
I think this should be resolved with #1082 (which has screenshots to show the re-added feature). Please let me know if there is a problem with it.
from hackage-server.
Closing as resolved.
from hackage-server.
Related Issues (20)
- Downloads statistics is not working for several packages HOT 1
- Hackage accepts `.cabal` files with 2 `source-repository head` entries HOT 2
- Unique filenames for `$revision.cabal`. HOT 7
- "curl: (56) Failure when receiving data from the peer" when trying to upload HOT 7
- Hackage search showing package version inconsistency HOT 18
- Support two factor authentication HOT 2
- Cannot run shell script as a preprocessor HOT 2
- Allow uploading docs as tar.gz HOT 1
- downloads counts stored inefficiently.
- Support tar-0.6
- Replicating coverage report on user side HOT 2
- Use newer GHC version to compile? HOT 2
- Feature: Download link for revised packages
- Hackage rejects valid SPDX license bzip2-1.0.6 HOT 12
- quotes have very inaccessible / illegible styling
- new packages in inconsistent state HOT 2
- Docbuilder fails if package requests newer build-tool
- Broken documentation link HOT 1
- Actual login page instead of Basic Auth
- Only notify about dependencies that bumped to next major version HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hackage-server.