Project

General

Profile

Actions

Bug #20397

open

The nkf license in LEGAL file seems to be obsolete

Added by vo.x (Vit Ondruch) 2 months ago. Updated about 2 months ago.

Status:
Open
Assignee:
-
Target version:
-
ruby -v:
ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux]
[ruby-core:117347]

Description

The LEGAL file seems to contain obsolete information about nkf license.

It seems that nkf indeed use such license, but in upstream, it was first changed to MIT and then immediately to zlib license.

Ruby has picked up that change with git|13313688b243882aff7815598ddd9fcbae69bc17

Maybe @naruse (Yui NARUSE) can comment about this.

Updated by shyouhei (Shyouhei Urabe) about 2 months ago

nkf is out of tree these days. Just clearing that section should suffice I think.

Updated by vo.x (Vit Ondruch) about 2 months ago

shyouhei (Shyouhei Urabe) wrote in #note-1:

nkf is out of tree these days. Just clearing that section should suffice I think.

Well, nkf is part of all currently supported Ruby releases.

Nevertheless, I have also opened ticket here, because the current situation is quite unclear to me. For example the .gemspec file claims Ruby OR BSD-2-Clause licenses since git|2e3a7f70ae71650be6ea38a483f66ce17ca5eb1d despite the LEGAL file saying something different.

Updated by shyouhei (Shyouhei Urabe) about 2 months ago

Yes, releases do include nkf. But the repo is split. I think nkf's situation shall be cleared for its own sake. LEGAL should no longer be the primary source of truth for that library.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0