You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Effectively reopening #769, which said to fix the issue, but as of onefetch 2.19.0 it still is reproducible
Possible Solution 馃挕
To my knowledge, the or-later is determined by the license headers in the files. If scanning the licensed files is impractical to determine the or-later, maybe removing the only in the license printed helps remove a degree of confusion.
The text was updated successfully, but these errors were encountered:
As suggested in Wrong license detected: GPL-3.0-only聽#769, get the license value from the package manifest first (only works for Cargo.toml or pakage.json) -> already implemented
In doubt (presence of aliases) show both licenses to the user, smth like License: GPL-3.0-or-later | GPL-3.0-only
For reference, it seems like the library used by github for license detection has the same issue licensee/licensee#406 and their solution matches @streaksu's suggestion
Perhaps Askolono can also report simplified names (e.g. gpl-3.0-* -> GPL 3.0) as an additional field if it doesn't already? And then we could use those.
Duplicates
Current behavior 馃槸
Expected behavior 馃
Steps to reproduce 馃暪
onefetch
insideAdditional context/Screenshots 馃敠
Effectively reopening #769, which said to fix the issue, but as of
onefetch 2.19.0
it still is reproduciblePossible Solution 馃挕
To my knowledge, the
or-later
is determined by the license headers in the files. If scanning the licensed files is impractical to determine theor-later
, maybe removing theonly
in the license printed helps remove a degree of confusion.The text was updated successfully, but these errors were encountered: