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
Hello, I have some questions regarding the Syft code that I'd like to ask. In pkg/cataloger/debian/dependency.go and pkg/cataloger/redhat/dependency.go, after retrieving Requires, how are the dependencies resolved from require to specific Linux software packages? For example, in Fedora, when analyzing the dependency list of a binary package, it might include /bin/sh and libc.so.6(GLIBC_2.38)(64bit). How are these dependencies eventually resolved into a concrete package list (e.g., bash and glibc)? Thank you!
The text was updated successfully, but these errors were encountered:
Hello, I have some questions regarding the Syft code that I'd like to ask. In pkg/cataloger/debian/dependency.go and pkg/cataloger/redhat/dependency.go, after retrieving Requires, how are the dependencies resolved from require to specific Linux software packages? For example, in Fedora, when analyzing the dependency list of a binary package, it might include /bin/sh and libc.so.6(GLIBC_2.38)(64bit). How are these dependencies eventually resolved into a concrete package list (e.g., bash and glibc)? Thank you!
The text was updated successfully, but these errors were encountered: