When dealing with license text you must go literal with every single word. It says you must include the copyright notice _and_ the permission notice you are reading, so your approach is legally "incorrect". An easy way to solve this would be to just include a text file with both notices in your software package, e.g., "Enet.txt".
On Fri, Mar 25, 2011 at 5:21 PM, Philip Bennefall <[email protected]>wrote: > Hi Lee, > > I just had a quick question for you regarding the ENet license, to make > sure I am doing things correctly. With the following statement: > > > The above copyright notice and this permission notice shall be included in > all copies or substantial portions of the Software. > > > > Do you refer to the source code, or must binary applications that use ENet > include the license? Currently I have a statement like this in my > documentation (including a link to the website): > > > > The ENet Project <http://enet.bespin.org/> > ENet is a rock solid layer on top of the UDP protocol, optimized especially > for high-speed games. This is what BGT uses to provide its networking > capabilities. > > Is this acceptable? Or am I required to add the full legal text? I much > prefer the above notice to the complete license. > > > > Thanks! > > > > Kind regards, > > > > Philip Bennefall > > _______________________________________________ > ENet-discuss mailing list > [email protected] > http://lists.cubik.org/mailman/listinfo/enet-discuss > >
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
