Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion of JGF metadata included #1

Open
vsoch opened this issue Jun 5, 2024 · 1 comment
Open

Discussion of JGF metadata included #1

vsoch opened this issue Jun 5, 2024 · 1 comment

Comments

@vsoch
Copy link
Member

vsoch commented Jun 5, 2024

Right now, I am doing the following structure (for nodes)

spack root
  package --> name@version
  contains -- [lib] --> <library>
  contains -- [lib] --> <library>
  contains -- [bin] --> <binary>

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.

@vsoch
Copy link
Member Author

vsoch commented Jun 5, 2024

Easy idea for making this smaller - only represent one way of the edge (so one of "contains" or "in" but not both).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant