Flox info <packageName>

Feature Requests
1

Hi. I’m very excited to use flox instead of homebrew. I like to use the command brew info to get information about package dependencies, link to homepage/recipe etc…

➜  ~ brew info ripgrep
==> ripgrep: stable 13.0.0 (bottled), HEAD
Search tool like grep and The Silver Searcher
https://github.com/BurntSushi/ripgrep
/usr/local/Cellar/ripgrep/13.0.0 (13 files, 6.2MB) *
  Poured from bottle on 2021-06-13 at 16:32:29
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/ripgrep.rb
License: Unlicense
==> Dependencies
Build: asciidoctor ✘, pkg-config ✔, rust ✘
Required: pcre2 ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
fish completions have been installed to:
  /usr/local/share/fish/vendor_completions.d
==> Analytics
install: 237 (30 days), 18,944 (90 days), 111,871 (365 days)
install-on-request: 234 (30 days), 18,603 (90 days), 109,059 (365 days)
build-error: 0 (30 days)

or on NixOS

➜  ~ nix-env -qa --description ripgrep
ripgrep-13.0.0  A utility that combines the usability of The Silver Searcher with the raw speed of grep
➜  ~ nix-env -qa --description --meta --json ripgrep
{
  "nixpkgs.ripgrep": {
    "meta": {
      "available": true,
      "broken": false,
      "description": "A utility that combines the usability of The Silver Searcher with the raw speed of grep",
      "homepage": "https://github.com/BurntSushi/ripgrep",
...
2

Thanks for the recommendation. I agree that having a flox info or flox show command would be useful.

For now if you want info on a package’s dependencies you’ve got there’s this ( less than ideal ) way to look that up, you can also add --json to this:

~ % flox nix path-info $( flox nix build nixpkgs-flox\#hello --no-link --print-out-paths; ) -r;
/nix/store/jdjpni8kq3i95dj1d49nlf9m10wl0kqq-libunistring-1.0
/nix/store/na1irnycfp8z5mab0g5jvrnhnscsaqsb-libidn2-2.3.2
/nix/store/lqz6hmd86viw83f9qll2ip87jhb7p1ah-glibc-2.35-224
/nix/store/260q5867crm1xjs4khgqpl6vr9kywql1-hello-2.12.1
3

Hi @yurtaev, thank you so much for this feature request! We have logged it internally for prioritisation. and look forward to rolling this out in a future release.

1 Like