From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] add a reference to the official SPDX License List
Date: Tue, 6 Dec 2022 18:39:43 -0700 [thread overview]
Message-ID: <b318c461-8f14-96ba-8594-9e945ca18a2e@SystematicSw.ab.ca> (raw)
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
next reply other threads:[~2022-12-07 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 1:39 Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 17:25 Chad Dougherty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b318c461-8f14-96ba-8594-9e945ca18a2e@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).