-
Notifications
You must be signed in to change notification settings - Fork 20
Spec: Define "DEP5" #30
Comments
To summarise, the suggestion was:
To which the concern was that DEP5 has some relevant differences to SPDX, most relevantly in some license names, so for REUSE a more “SPDX flavour” of DEP5 would be needed. Which may mean we would need to define a new file format for this use which would be basically DEP5, but with SPDX Short Identifiers instead of Debian’s. |
I think instead of defining "DEP5 File", it makes more sense to define "DEP5". So perhaps something simple like: DEP5 - Machine-readable It may be nice to state what those different things are, but they are evident from the spec, and I don't really want to repeat myself. |
I think this approach is an elegant solution, yes. Perhaps it would make sense to explicitly state that SPDX takes precedence over DEP5, because that is basically where REUSE clashes with DEP5. |
I agree, for the spec that's a nice solution to prevent repeating ourselves. I we wanted to add this to the FAQ, we should link to resources where such differences are explained. |
Closed by 8b5ca93 |
Thread: #23 (comment)
@silverhook @carmenbianca
The text was updated successfully, but these errors were encountered: