| Summary: | sys-kernel/linux-firmware: missing license? (vs sys-firmware/radeon-ucode) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
| Component: | Current packages | Assignee: | Chí-Thanh Christopher Nguyễn <chithanh> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kernel, licenses, zerochaos |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Michał Górny
2017-04-20 07:10:57 UTC
LICENSE is a long-standing issue in the linux-firmware package, attempting to enumerate them all (and keep them updated) is a lot of work that nobody is willing to do currently. Most of the non-free licenses like radeon-ucode would presumably qualify as freedist. I wouldn't mind making it freedist. However, I feel like the current text of freedist is far from useful. Maybe it'd make sense to expand it a bit and explain the usual terms and limitations. (In reply to Chí-Thanh Christopher Nguyễn from comment #1) > LICENSE is a long-standing issue in the linux-firmware package, attempting > to enumerate them all (and keep them updated) is a lot of work that nobody > is willing to do currently. Well, I had sent an e-mail on the issue to maintainers in February of 2013, together with a first draft putting things into three categories (attached to bug 318841). GregKH followed up on it and it went as far as the Technical Advisory board of the Linux Foundation who approved that the work should be done (and IIUC tasked Greg with it). A reminder was sent in May 2013, but we never got any reply. > Most of the non-free licenses like radeon-ucode would presumably qualify as > freedist. Yes, most but not all. Last time I looked, about one third of them was not distributable. Which is enough to make the whole package non-redistributable. radeon-ucode is gone This is part of the more general issue in bug 318841, therefore resolving as duplicate of that bug. *** This bug has been marked as a duplicate of bug 318841 *** |