Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#28772 - [licenses] Add MIT License as a common license
Attached to Project:
Arch Linux
Opened by Wander Nauta (wandernauta) - Sunday, 04 March 2012, 14:58 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 March 2012, 21:44 GMT
Opened by Wander Nauta (wandernauta) - Sunday, 04 March 2012, 14:58 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 March 2012, 21:44 GMT
|
DetailsThe MIT ('Expat') license [1] is used by high-visibility projects like Rails and Lua [2], jQuery, and lots of smaller projects as well. It's OSI-approved and seems more widely-used than most other licenses in the 'common' directory [3].
Please add it as a common license. Thanks! [1] http://www.opensource.org/licenses/MIT [2] http://en.wikipedia.org/wiki/MIT_License [3] http://osrc.blackducksoftware.com/data/licenses/ 
license.txt
(1 KiB)
|
This task depends upon
The MIT, BSD, zlib/libpng and Python licenses are special cases and cannot be included in the 'common' licenses pkg. For the sake of the license variable, it's treated like a common license (license=('BSD'), license=('MIT'), license=('ZLIB') or license=('Python')) but for the sake of the filesystem, it's a custom license, because each one has its own copyright line. Each MIT, BSD, zlib/libpng or Python licensed package should have its unique license stored in /usr/share/licenses/$pkgname/.