How will Entropic achieve package management for anything?

Hello,

Recently watched ceejbot's talk on Entropic and the state of npm and I'm honestly hyped for a federated package manager for my JS projects, but it seems highlighted in the readme that Entropic will be a package manager for anything, meaning that one may wish to host their own server locally that distributes other forms of packages for another language or not a language at all. Maybe it's audio files, who knows, it shouldn't matter.

This issue is to raise the question, do we have a story for this? How will the cli address installation of packages, is it entirely agnostic of the project? Are there ideas on this already? Would be good to have Chris and C J weigh in on this.

Start by reading the README statement that Entropic is a package registry for anything, then examine the CLI's package-installation approach. The issue does not name files or tests; done would require an agreed story for installing non-JavaScript packages and documenting whether the CLI is project-agnostic.

Written by the indexing model from the issue text.