From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: LICENSE (was Re: [ITP] asr-manpages, funny-manpages)
Date: Sat, 4 Jun 2022 10:20:39 -0600 [thread overview]
Message-ID: <695c721b-3d56-2aa2-5afc-ad2d83b9fd08@SystematicSw.ab.ca> (raw)
In-Reply-To: <ba0d5be4-9a36-3675-c5ed-6cc6d5ef31da@dronecode.org.uk>
On 2022-06-04 07:02, Jon Turney wrote:
> On 14/05/2022 14:15, Jon Turney wrote:
>> On 08/05/2022 18:49, Brian Inglis wrote:
>>> On 2022-05-08 09:15, Libor Ukropec wrote:
>>>> Dne 07.05.2022 v 20:52 Brian Inglis napsal(a):
>>>> BTW, I noted LICENSE, CYGWIN_MAINTAINER, UPSTREAM_MAINTAINER
>>>> variables ... are they used/shown somewhere and is it a best
>>>> practise to have them in the cygport script?
>>>
>>> Something I think should be documented somewhere, are tracked in some
>>> other distros package trackers, easier to add on adoption, and useful
>>> when you want to submit bug reports upstream.
>>> Defining then as shell vars mean you can use them for searching or in
>>> commands.
>>
>> 'LICENSE' probably should be required by cygport, containing a SPDX ID
>> or license expression.
>>
>> I'm not sure about 'CYGWIN_MAINTAINER', since we already track that
>> information elsewhere.
> I am tinkering with adding support for LICENSE in cygport-> license: in
> src.hint, exposing that in the package summary data, backfilling from
> existing cyports and validating those as SPDX license expressions.
>
> I see that you've used:
>
> LICENSE=MIT-like
> LICENSE_SPDX="SPDX-License-Identifier: MIT-like"
>
> I don't see 'MIT-like' on https://spdx.org/licenses/, so I wonder if you
> could explain where that comes from?
Articles on early SPDX usage had suggestions for as yet uncatalogued
licences like adding -like. From the looks of my package sources, some
licensing info came from Fedora specs and conversions to cygport. My
cygports have now been updated locally to what I believe are correct
SPDX ids from the latest list. I have a number yet to add but build and
packaging issues take priority for time over info tweaks.
curl/curl.cygport:LICENSE=curl
curl/curl.cygport:LICENSE_SPDX="SPDX-License-Identifier: curl"
curl/curl-spec-fedora.cygport:LICENSE=MIT
curl/curl-spec-fedora.cygport:LICENSE_SPDX="SPDX-License-Identifier: MIT"
curl/curl-spec-opensuse.cygport:LICENSE=curl
curl/curl-spec-opensuse.cygport:LICENSE_SPDX="SPDX-License-Identifier: curl"
curl/mingw64-i686-curl.cygport:LICENSE=curl
curl/mingw64-i686-curl.cygport:LICENSE_SPDX="SPDX-License-Identifier: curl"
curl/mingw64-x86_64-curl.cygport:LICENSE=curl
curl/mingw64-x86_64-curl.cygport:LICENSE_SPDX="SPDX-License-Identifier:
curl"
man-pages-linux/man-pages-linux.cygport:LICENSE=verbatim
man-pages-linux/man-pages-linux.cygport:LICENSE_SPDX="SPDX-License-Identifier:
Linux-man-pages-copyleft"
man-pages-posix/man-pages-posix.cygport:LICENSE=verbatim
man-pages-posix/man-pages-posix.cygport:LICENSE_SPDX="SPDX-License-Identifier:
Linux-man-pages-copyleft
vttest/vttest.cygport:LICENSE=BSD
vttest/vttest.cygport:LICENSE_SPDX="SPDX-License-Identifier:
BSD-Source-Code"
vttest/vttest-spec-fedora.cygport:LICENSE=MIT
vttest/vttest-spec-fedora.cygport:LICENSE_SPDX="SPDX-License-Identifier:
MIT"
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-06-04 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 18:52 [ITP] asr-manpages, funny-manpages Brian Inglis
2022-05-08 15:15 ` Libor Ukropec
2022-05-08 17:49 ` Brian Inglis
2022-05-14 13:15 ` Jon Turney
2022-06-04 13:02 ` LICENSE (was Re: [ITP] asr-manpages, funny-manpages) Jon Turney
2022-06-04 16:20 ` Brian Inglis [this message]
2022-05-14 13:09 ` [ITP] asr-manpages, funny-manpages Jon Turney
2022-05-14 18:24 ` Brian Inglis
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=695c721b-3d56-2aa2-5afc-ad2d83b9fd08@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@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).