Date: Wed, 31 Jan 2018 19:45:40 +0000
From: =?iso-8859-1?B?Q+Fn?= <ca6c@bitmessage.ch>
To: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] RFC: Fixing license field in APKBUILDs (or a bit
 more)
Message-ID: <20180131194540.GA21821@alpine.my.domain>
References: <1614404acdb.edd44d4135179.3833405768989653606@zoho.com>
 <CA+T2pCGAS+ehDKb60JQR8J6ixASGfjfOzQQe4A-UCgHFg=1K2A@mail.gmail.com>
 <CA+T2pCFFNCc+tk-tsjHnRzsEB3X_CNbRRysA2qf5PtvU0MGp=g@mail.gmail.com>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <CA+T2pCFFNCc+tk-tsjHnRzsEB3X_CNbRRysA2qf5PtvU0MGp=g@mail.gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)

William Pitcock wrote:
=20
> After discussing with jirutka, we came to the conclusion that SPDX 2
> shorthand identifiers are fine as long as they are not vague.  For
> example "GPL-2.0+" is equally valid to "GPL-2.0-or-later".  This
> resolves the main gripe that Adelie has with SPDX 3.

Dear,

I've just worked with the sc package that happens to be in the public
domain. SPDX doesn't mention how to spell it. Should it be "public
domain", "Public Domain", "Public-Domain" or something else?

Thanks

--=20
ca=F3c



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---