Michal Marek wrote: > Johannes Meixner wrote: >> Hello, >> >> On Jul 24 14:17 Marcus Rueckert wrote: >>> as the symlink points to filenames which is the md5sum of the license >>> itself. i think this is not an issue. >> Can you explain in a bit more detail how such symlinks and >> filenames make sure that the right license texts are installed >> in the run-time system in any case? > > The filename is an md5sum of the license text. So a new version of the > "same" (as in same name) license will have a different filename. So if > you link to /.../ebf4e8b49780ab187d51bd26aaa022c6, it will allways be > that exact version of the GPL2 license.
What if in the source package, the license file contains (by mistake) an additional newline? Who should do the actual checking, that the license is really GPL (whatever else)? In this hash scheme, how can user display license using pager or editor? Also note that some packages have slightly modified licenses (like: author allows linking against some non-GPLed library) - will these licenses be bundled together with those "standard" ones? Petr p.s.: gzipped GPL2 = 7kB --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
