From: Charles McGarvey Date: Sat, 16 Jul 2011 19:49:35 +0000 (-0600) Subject: fixed documentation about where to find licenses X-Git-Url: https://git.dogcows.com/gitweb?p=chaz%2Fyoink;a=commitdiff_plain;h=8089e9f26d9fe0bd6037f2402a211d29492ad7c6 fixed documentation about where to find licenses --- diff --git a/README b/README index b993ffd..698d3c8 100644 --- a/README +++ b/README @@ -30,9 +30,10 @@ DESCRIPTION LICENSE The new code is released under the 2-clause BSD license. The old code - and original resources are provided under the zlib/libpng License. See - the COPYING file for complete details. The full texts of applicable - licenses can be found in doc/licenses within the Yoink package. + and original resources are provided under the zlib/libpng license. See + the file COPYING for complete details. Other parts are distributed under + different licenses. See yoink_license(7) for the full texts of the + relevant licenses. ABOUT THE CODE The code is a complete rewrite, containing none of the original code. diff --git a/doc/yoink_readme.7 b/doc/yoink_readme.7 index c35ae2d..6ce832b 100644 --- a/doc/yoink_readme.7 +++ b/doc/yoink_readme.7 @@ -43,12 +43,12 @@ for a more detailed discussion about the build system and a list of required packages. .Ss LICENSE The new code is released under the 2-clause BSD license. The old code and -original resources are provided under the zlib/libpng License. See the +original resources are provided under the zlib/libpng license. See the file .Pa COPYING -file for complete details. The full texts of applicable licenses can be -found in -.Pa doc/licenses -within the Yoink package. +for complete details. Other parts are distributed under different licenses. +See +.Xr yoink_license 7 +for the full texts of the relevant licenses. .Ss ABOUT THE CODE The code is a complete rewrite, containing none of the original code. I've made some effort to put the more generic or reusable code into a separate @@ -109,7 +109,7 @@ that, please observe the following: Stick to the coding style of the source code files you edit. Follow the general style of method and variable naming, as well as white space formatting. In particular, use literal tabs with an assumed tabstop of 8 -characters. Also, try to limit line lengths to 75 characters. +characters. Also, try to limit line lengths to 78 characters. .It For legal reasons, don't include other peoples' code with your patch. You must also agree to license your changes according to the same terms and