"jochen georges" <[email protected]> wrote in message news:[email protected]...
/* * ==================================================================== * * The Clearthought Software License, Version 2.0 * * Copyright (c) 2001 Daniel Barbalace. All rights reserved. * * Project maintained at https://tablelayout.dev.java.net * * I. Terms for redistribution of original source and binaries * * Redistribution and use of unmodified source and/or binaries are * permitted provided that the following condition is met: * * 1. Redistributions of original source code must retain the above * copyright notice and license. You are not required to redistribute * the original source; you may choose to redistribute only the * binaries. * * Basically, if you distribute unmodified source, you meet * automatically comply with the license with no additional effort on * your part.
Unmodified redistribution in source and binary forms are effectively conditionless. This is good.
* II. Terms for distribution of derived works via subclassing and/or * composition. *
This section can be ignored, as long as all derivities are made using section 3.
* * III. Terms for redistribution of source modified via patch files. * * You may generate derived works by means of patch files provided * that the following conditions are met: * * 1. Redistributions of original source code must retain the above * copyright notice and license. You are not required to * redistribute the original source; you may choose to redistribute * only the binaries resulting from the patch files.
That is all fine.
* 2. The original source files are not altered. All alteration is * done in patch files. *
This is explicitly allowed by DFSG 4.
* 3. Derived works are not contained in the info.clearthought * namespace/package or any subpackage of info.clearthought. This * means that your patch files must change the namespace/package * for the derived work. See section II for examples.
This one is tricky. This may be acceptable under DFSG 4. It is clearly within the spirit of DFSG 4.
* 4. Derived works do not use the class or interface names from the * info.clearthought... packages. This means your patch files * must change the names of the interfaces and classes they alter. * See section II for examples.
If each class/interface is considered a seperate work, then this is probably acceptable under DFSG 4.
* 5. Derived works must include the following disclaimer. * "This work is derived from Clearthought's TableLayout, * https://tablelayout.dev.java.net, by means of patch files * rather than subclassing or composition. Therefore, this work * might not contain the latest fixes and features of TableLayout."
This may be a problem. The idea here is to warn users that this, although a derivitive of the TableLayout package, will not automatically inherit the latest fixes and patches by merely installing the Tablelayout Java classes.
* IV. Terms for repackaging, transcoding, and compiling of binaries. * * You may do any of the following with the binaries of the * original software.
These are additional permissions for binary files. This basically is giving explict permission to transform the binaries to whatever form is most suitable. I see no issue here.
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE AUTHOR, AFFILATED BUSINESSES, * OR ANYONE ELSE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== */
Reasonably standard disclaimer. There are no freeness issues here, that i can see.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
