Re: Followup question after Linuxcon talk

Lamons, Scott (Open Source Program Office) <scott.lamons@...>


Thanks for your message and joining the list. You pose an interesting scenario! While the SPDX is typically provided with the corresponding code I suspect there might be some way that this could be accomplished or communicated -- perhaps using some of the comment fields or maybe it makes sense to create and contribute SPDX for the code you're not shipping but I will defer to the technical experts on the list.

Scott Lamons
SPDX Business Team

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Bracewell, Robert
Sent: Thursday, August 30, 2012 9:03 PM
To: spdx@...
Subject: Followup question after Linuxcon talk

Thanks for a great discussion on spdx its got me interested in wrapping spdx into my current release activities as a release manager.

Say for example I ship an SDK and for a customer to use this SDK they need to download a number of other files that were unable to ship within the package. What would be the best way with spdx to indicate such? Ideally if I could ship them I would but for reasons outside of my control I am unable to do so.

To date I have been using Nexus pro to decorate the artifacts that make up the bill of materials by adding metadata to this tool. The metadata i've been storing is inline with what spdx already tracks. I wrote my own Maven plugins to take care of the metadata aspect of adding it and pulling it out of Nexus when producing the bill of materials. What I am thinking is that instead of storing metadata i'll just attach an spdx file as an attached artifact with a classifier and for every artifact that is subsequently packaged it will just pull down the spdx files and aggregate.

Looks like I need to do some reading of the spec and whitepapers etc to get up to speed.

Spdx mailing list

Join { to automatically receive all group messages.