public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
* Re: [PATCH] add a reference to the official SPDX License List
@ 2022-12-07  1:39 Brian Inglis
  0 siblings, 0 replies; 2+ messages in thread
From: Brian Inglis @ 2022-12-07  1:39 UTC (permalink / raw)
  To: Cygwin Patches

Spec link is already 404, so brittle, not necessarily current, and that licence 
list appendix is only informative and not current, so link to the actual current 
license list instead:

	https://spdx.org/licenses/

and provide a link to the generic current spec page which offers different formats:

	https://spdx.dev/specifications/#current-version

with something like (hacked from previous email):

diff --git a/packaging-hint-files.html b/packaging-hint-files.html
--- a/packaging-hint-files.html
+++ b/packaging-hint-files.html
@@ -406,7 +406,7 @@ version: <i>version</i>
      <p>
-      <code>license</code> is
-      a <a href="https://spdx.github.io/spdx-spec/SPDX-license-expressions/">SPDX
-      license expression</a> for the <a href="https://spdx.org/licenses/">open 
source license(s)</a> of the package
+      <a href="https://spdx.org/licenses/"><code>license</code></a> is an SPDX
+      <a href="https://spdx.dev/specifications/#current-version">license 
expression</a>
+      for the open source license(s)</a> of the package
        source code.
      </p>
    </li>

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [PATCH] add a reference to the official SPDX License List
@ 2022-10-07 17:25 Chad Dougherty
  0 siblings, 0 replies; 2+ messages in thread
From: Chad Dougherty @ 2022-10-07 17:25 UTC (permalink / raw)
  To: cygwin-patches; +Cc: Chad Dougherty

this page contains the concrete license identifiers that packagers are
likely to want to include in their cygport files

I found this list quite useful and had several slightly incorrect
variations in my first attempt at creating a cygport before discovering
it.

Signed-off-by: Chad Dougherty <crd@acm.org>
---
 packaging-hint-files.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packaging-hint-files.html b/packaging-hint-files.html
index 38ea2c8e..8c299ba3 100755
--- a/packaging-hint-files.html
+++ b/packaging-hint-files.html
@@ -406,7 +406,7 @@ version: <i>version</i>
     <p>
       <code>license</code> is
       a <a href="https://spdx.github.io/spdx-spec/SPDX-license-expressions/">SPDX
-      license expression</a> for the open source license(s) of the package
+      license expression</a> for the <a href="https://spdx.org/licenses/">open source license(s)</a> of the package
       source code.
     </p>
   </li>
-- 
2.38.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-12-07  1:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-07  1:39 [PATCH] add a reference to the official SPDX License List Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2022-10-07 17:25 Chad Dougherty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).