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
And then the idea is that the edges are between packages and the libs and binaries - that seems like the level of what a user would look for. I've packaged additional metadata about a package with the node under "attributes" - a similar custom subsection to "paths." But even with a "small" spack install, it's huge. See: https://gist.github.com/vsoch/af1c57b558a476d1bb67fd78b284677e.
We likely want to discuss this structure and possibly trim away what is not needed to solve the immediate problem. It could also be the case we aren't interested in every package of a spack install, but it's hard to say how to make that decision.
The text was updated successfully, but these errors were encountered:
Right now, I am doing the following structure (for nodes)
And then the idea is that the edges are between packages and the libs and binaries - that seems like the level of what a user would look for. I've packaged additional metadata about a package with the node under "attributes" - a similar custom subsection to "paths." But even with a "small" spack install, it's huge. See: https://gist.github.com/vsoch/af1c57b558a476d1bb67fd78b284677e.
We likely want to discuss this structure and possibly trim away what is not needed to solve the immediate problem. It could also be the case we aren't interested in every package of a spack install, but it's hard to say how to make that decision.
The text was updated successfully, but these errors were encountered: