-
Notifications
You must be signed in to change notification settings - Fork 38
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
How can i refer 2 spdxs in third spdx file and access all the packages information from 3rd spdx file #131
Comments
@goneall Any comments/suggestions on above ? |
@rakeshsrinivasa If you want to refer to packages in spdx_1 and spdx_2, you would use the
You would then refer to the package using the syntax |
A couple other things in looking through the attached files:
|
@goneall In the below externalDocumentRefs:
Where am i specifying the local path of spdx_1 or spdx_2 file . How does the spdx_3 yaml file determine which local file it has to refer ? |
@goneall Btwn did you get a chance to look at the attached github.zip ? Any comments on that |
@rakeshsrinivasa There isn't a field for the local path of the externally referenced files. We discussed adding it to the spec and decided not to since files may move etc. You can probably add an |
Just briefly, see the comment above for some feedback. |
@rakeshsrinivasa Just checking to see if you still had any questions on this issue - you can also post to the SPDX Tech team mailing list for additional support with the spec. |
Suppose Assume that i have a spdx file called "spdx_1.yaml" and another one called "spdx_2.yaml" . Both these spdx files has certain packages. Now i want to create another spdx file (call spdx_3.yaml) which just refers spdx_1 and spdx2 yaml files available locally in the same folder.
Now using spdx-tools java i need to access all the packages available in spdx_1 and spdx_2 yamls Via spdx_3.yaml.
Below is my questions
1.
I am facing difficulties in forming spdx_3.yaml .Please do verify and help me
github.zip
Thanks in advance
The text was updated successfully, but these errors were encountered: