Open haakon-e opened 2 weeks ago
While I understand it can be nice to do everything from Pkg itself I am not sure it is worth spending much effort on to this when you can just go to https://juliahub.com/ui/Packages/ or https://juliapackages.com/ etc and have a much better experience with graphs and tables etc than what Pkg can ever provide.
Pkg
has seen amazing improvements in the past few versions, with indicators for packages that are upgradeable, hindered from being upgraded, and so on.One feature I'm missing that I've found in other ecosystems is a "search" functionality with some basic information about the packages.
Personally, I'm most interested in learning about package versions and url, a small blurb/about-me could be useful too (see related discussions below for potential approaches)
I'm envisioning something along the lines of:
Below is a quickly hacked together code for obtaining version history for a given package in the General registry, mostly achieved by poking into
Pkg
s existing internals (e.g.Pkg.status()
,Pkg.print_status(...)
,Pkg.Types.Context()
)Having written the code first, then discovered all the discussion about this already (as one does...), I realize more thinking may be needed to hone down a really great long-term interface. That said, I hope a variant of this suggestion can be a small, but practically achievable step, in this direction.
relevant issue(s): #3259, #2613, #1397 (with great discussion) Related to (but smaller(?) in scope than): discourse#98813 Tags/metadata aspect also described in: #1967, #1070 (includes similar code to the above) Similar goals, but web-based: https://juliapackages.com