> On Tue, Nov 15, 2022, 12:24 Miro Hrončok
>
>
>
> I package askalono-cli which can detect license texts and outputs an SPDX
> identifier: https://github.com/jpeddicord/askalono
>
> We use it in go2rpm.
>
Looking through this thread, it seems there are a range of tools that package
maintai
Dne 16. 11. 22 v 7:47 Bob Mauchin napsal(a):
I package askalono-cli which can detect license texts and outputs an SPDX identifier:
https://github.com/jpeddicord/askalono
This is is great. I have added it to Change documentation.
Mirek
___
devel mai
On Tue, Nov 15, 2022, 12:24 Miro Hrončok wrote:
> On 14. 11. 22 20:53, Miroslav Suchý wrote:
> > 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> identify
> > your license. This is a Chrome and Firefox plugin and allows you to
> select the
> > text; and in the context menu
Dne 15. 11. 22 v 10:44 Daniel P. Berrangé napsal(a):
In that case, IMHO, the tool should NOT suggest a license from the
list at all, and definitely not arbitrarily suggest the last one it
loaded, which is highly likely to be wrong. If it wants to suggest,
then suggest the most likely option out o
On Tue, Nov 15, 2022, at 8:23 PM, Miro Hrončok wrote:
> On 14. 11. 22 20:53, Miroslav Suchý wrote:
>> 1) You can use https://github.com/spdx/spdx-license-diff and use it
>>to identify your license. This is a Chrome and Firefox plugin and
>>allows you to select the text; and in the context m
On Tue, Nov 15, 2022 at 12:17 PM Todd Zullinger wrote:
>
> Neal Gompa wrote:
> > On Tue, Nov 15, 2022 at 11:05 AM Todd Zullinger wrote:
> >> Am I missing something obvious or does licensecheck not work
> >> as expected? This is with licensecheck-3.3.0-2.fc36.noarch.
> >
> > licensecheck does not
Neal Gompa wrote:
> On Tue, Nov 15, 2022 at 11:05 AM Todd Zullinger wrote:
>> Am I missing something obvious or does licensecheck not work
>> as expected? This is with licensecheck-3.3.0-2.fc36.noarch.
>
> licensecheck does not follow/use SPDX-License-Identifier at all. It
> predates that scheme
On Tue, Nov 15, 2022 at 11:05 AM Todd Zullinger wrote:
>
> Neal Gompa wrote:
> > On Tue, Nov 15, 2022 at 6:24 AM Miro Hrončok wrote:
> >> Do we have a command line tool for this? Does licensecheck support SPDX
> >> identifiers?
> >>
> >> (I find the use of browser extension for this very weird. I
Neal Gompa wrote:
> On Tue, Nov 15, 2022 at 6:24 AM Miro Hrončok wrote:
>> Do we have a command line tool for this? Does licensecheck support SPDX
>> identifiers?
>>
>> (I find the use of browser extension for this very weird. I have the LICENSE
>> file unpackaged with the sources on my machine, I
On Tue, Nov 15, 2022 at 6:29 AM Miro Hrončok wrote:
>
> On 14. 11. 22 20:53, Miroslav Suchý wrote:
> > 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> > identify
> > your license. This is a Chrome and Firefox plugin and allows you to select
> > the
> > text; and in the c
Dne 15. 11. 22 v 10:44 Daniel P. Berrangé napsal(a):
Interestingly when I run 'license-fedora2spdx MIT' is just
always prints 'mpich2', and the list of suggestions is entirely
reversed from what you show here. Why 'mpich2' - it is simply
because it is last in the list to be loaded. This is rathe
On Tue, Nov 15, 2022 at 6:24 AM Miro Hrončok wrote:
>
> On 14. 11. 22 20:53, Miroslav Suchý wrote:
> > 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> > identify
> > your license. This is a Chrome and Firefox plugin and allows you to select
> > the
> > text; and in the c
On 14. 11. 22 20:53, Miroslav Suchý wrote:
1) You can use https://github.com/spdx/spdx-license-diff and use it to identify
your license. This is a Chrome and Firefox plugin and allows you to select the
text; and in the context menu, you can choose to identify the license. It will
print, e.g., t
On Mon, Nov 14, 2022 at 08:53:09PM +0100, Miroslav Suchý wrote:
> MIT and BSD are very common licenses and can be tricky to convert to SPDX
> license identifiers. Just today, I got two questions about it. We have this
> covered in FAQ
>
> https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_
V Mon, Nov 14, 2022 at 08:53:09PM +0100, Miroslav Suchý napsal(a):
> There are two common ways to find out what SPDX identifier you should use in
> such cases.
>
>
> 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> identify your license. This is a Chrome and Firefox plugi
On Mon, Nov 14, 2022 at 3:29 PM Miroslav Suchý wrote:
> Until now, what Fedora described as an "MIT" license was, in fact, a whole
> family of licenses. SPDX identify them differently. And the differences can
> be subtle. E.g., compare
>
> https://spdx.org/licenses/MIT.html
> https://spdx.org/l
Miroslav Suchý wrote:
> There are two common ways to find out what SPDX identifier you should use
> in such cases.
>
>
> 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> identify your license. This is a Chrome and Firefox plugin and allows you
> to select the text; and in
MIT and BSD are very common licenses and can be tricky to convert to SPDX license identifiers. Just today, I got two
questions about it. We have this covered in FAQ
https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1#I_have_a_package_with_BSD_or_MIT_in_the_License_field,_how_do_I_conver
18 matches
Mail list logo
