--- nqc-3.1.r6.orig/Makefile +++ nqc-3.1.r6/Makefile @@ -86,7 +86,7 @@ ifneq (,$(strip $(findstring $(OSTYPE), Linux))) # Linux # uncomment this next line if you have the USB tower library installed -# USBOBJ = rcxlib/RCX_USBTowerPipe_linux.o + USBOBJ = rcxlib/RCX_USBTowerPipe_linux.o CFLAGS += -I/usr/local/include/LegoUSB -Wno-deprecated else ifneq (,$(findstring $(OSTYPE), SunOS)) --- nqc-3.1.r6.orig/compiler/Error.cpp +++ nqc-3.1.r6/compiler/Error.cpp @@ -24,6 +24,9 @@ #include "Error.h" #include "LexLocation.h" +#define __STDC_FORMAT_MACROS +#include + using std::sprintf; static const char *sErrorText[] = { @@ -53,8 +56,8 @@ "expression is not a legal target for assignment", "undefined task \'%s\'", - "maximum of %d subroutines exceeded", - "maximum of %d tasks exceeded", + "maximum of %"PRIdPTR" subroutines exceeded", + "maximum of %"PRIdPTR" tasks exceeded", "initialization function \'%s\' is not defined", "task \'main\' not defined", "\'continue\' is only valid within a loop", @@ -95,7 +98,7 @@ "label \'%s\' redefined", "illegal resource type", - "maximum of %d resources of this type exceeded", + "maximum of %"PRIdPTR" resources of this type exceeded", "cannot take the address of an array with a non-constant index", --- nqc-3.1.r6.orig/nqc-man-2.1r1-0.man +++ nqc-3.1.r6/nqc-man-2.1r1-0.man @@ -72,7 +72,7 @@ extension of \fI\.rcx\fR instead of \fI\.nqc\fR. .TP \fB\-S\fR\fIportname\fR -use serial port \fIportname\fR. Under Linux, \fI/dev/ttyS0\fR is the +use serial port \fIportname\fR. Under Linux, \fI/dev/rcx\fR is the default. (This will differ on other platforms.) The port can also be specified via the RCX_PORT environment variable, but the command line option takes precedence. --- nqc-3.1.r6.orig/platform/PSerial_unix.cpp +++ nqc-3.1.r6/platform/PSerial_unix.cpp @@ -38,7 +38,7 @@ #include "PSerial.h" #ifndef DEFAULT_SERIAL_NAME -#define DEFAULT_SERIAL_NAME "/dev/ttyS0" +#define DEFAULT_SERIAL_NAME "/dev/rcx" #endif --- nqc-3.1.r6.orig/rcxlib/RCX_USBTowerPipe_linux.cpp +++ nqc-3.1.r6/rcxlib/RCX_USBTowerPipe_linux.cpp @@ -59,7 +59,7 @@ return new RCX_USBTowerPipe_linux(); } -#define DEFAULT_TOWER_NAME "/dev/usb/lego0" +#define DEFAULT_TOWER_NAME "/dev/usb/legousbtower0" RCX_Result RCX_USBTowerPipe_linux::Open(const char *name, int mode) { --- nqc-3.1.r6.orig/rcxlib/LegoUSB/legousbtower.h +++ nqc-3.1.r6/rcxlib/LegoUSB/legousbtower.h @@ -0,0 +1,52 @@ +/* + * legousbtower Lego USB IR Tower Linux Driver + * + * Copyright (c) 2001-2002 The LegoUSB DevTeam + * + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License as + * published by the Free Software Foundation; either version 2 of + * the License, or (at your option) any later version. + * + */ + +#ifndef __LEGOUSBTOWER_H +#define __LEGOUSBTOWER_H + +#define LEGO_TOWER_SET_PARAM _IOW('u', 0xb0, int) +#define LEGO_TOWER_GET_PARAM _IOW('u', 0xb1, int) +#define LEGO_TOWER_RESET _IO('u', 0xb3) + + +#define LEGO_TOWER_SET_READ_TIMEOUT _IOW('u', 0xc8, int) +#define LEGO_TOWER_SET_WRITE_TIMEOUT _IOW('u', 0xc9, int) + + +#define LEGO_USB_TOWER_REQUEST_GET 1 +#define LEGO_USB_TOWER_REQUEST_SET 2 +#define LEGO_USB_TOWER_REQUEST_RESET 4 + + +#define LEGO_USB_TOWER_ADDRESS_MODE 1 +#define LEGO_USB_TOWER_ADDRESS_POWER_LEVEL 2 + +#define LEGO_USB_TOWER_POWER_LEVEL_LOW 1 +#define LEGO_USB_TOWER_POWER_LEVEL_MEDIUM 2 +#define LEGO_USB_TOWER_POWER_LEVEL_HIGH 3 + +#define LEGO_USB_TOWER_MODE_VLL 1 +#define LEGO_USB_TOWER_MODE_RCX 2 + + + +struct request_reply +{ + unsigned short length; + unsigned char error_code; + unsigned char value; + unsigned char buffer[16]; // variable replies from the tower + // at this stage we aren't interested in the data +}; + +#endif --- nqc-3.1.r6.orig/readme.txt +++ nqc-3.1.r6/readme.txt @@ -77,9 +77,9 @@ Linux: The syntax for setting environment variables is shell specific. By - default nqcc uses "/dev/ttyS0" as the device name for the serial - port. If you are using the second serial port, then "/dev/ttyS1" - should work. Other device drivers may or may not work depending on if + default nqcc uses "/dev/rcx" as the device name for the serial + port. You should set this up as a symlink to one of the "/dev/ttyS?" + devices. Other device drivers may or may not work depending on if they implement the expected ioctl's to setup the baud rate, parity, etc. --- nqc-3.1.r6.orig/debian/README.Debian +++ nqc-3.1.r6/debian/README.Debian @@ -0,0 +1,184 @@ +README.Debian for nqc -*- text -*- +===================== + +This version of nqc has been modified to default to device /dev/rcx +for downloading to the LEGO Mindstorms RCX. I recommend that you make +a symlink from /dev/rcx to the proper serial device for your system. +Typically, this is /dev/ttyS0 or /dev/ttyS1. Alternatively, you can +specify the serial device in a command-line option to the RCX +utilities as necessary. + +To connect via USB, you have two options. First, you can pass the +command line option "-Susb" to `nqc' each time you run it. Second, +you can set the environment variable `RCX_PORT' to `usb', using the +command + + export RCX_PORT=usb + +if you use the Bourne shell, or + + setenv RCX_PORT usb + +if you use the C shell. You can avoid typing this command each time +you log in by adding it to your .profile under the Bourne shell (or +.bash_profile under Bash) or to .cshrc under the C shell. + + +RCX for Linux Quick Start +========================= + +Before you start writing your own programs for the RCX, you need to +take care of a few things, explained below. Other than the RCX +hardware itself, this package includes almost everything you need to +get started. In addition, you'll need the CD that came with your +Robotics Invention System (RIS) kit, if you haven't already downloaded +the firmware to the RCX. + +Setup Hardware and Software +--------------------------- + +You need to set up the hardware and software that goes with your RCX +before you can use it with the computer. First, take the infrared +tower and plug it into an unused serial or USB port. + +Serial port: If you used a serial port, note which one it is. If +you're not sure, you can try port 0 first, then port 1 if that doesn't +work. Then become root and make a symlink from /dev/rcx to the +appropriate serial device, which is probably /dev/ttyS0 or /dev/ttyS1. +Typical commands for doing this are shown below (substitute ttyS1 for +ttyS0 if appropriate): + + # su + Password: + # cd /dev + # ln -si ttyS0 rcx + +Note that users who are allowed to access the RCX will need permission +to access /dev/rcx. One way to do this is by adding these users to +the `dialout' group, which by default under Debian GNU/Linux has +access to serial devices. You can add user `foo' to group `dialout' +with the command `adduser foo dialout'. Please note that such users +will have full access to all system serial devices. If this is +undesirable then you should implement a different group system for +device permissions. + +USB port: Before connecting to the RCX through a USB port, you need to +have the proper kernel driver. Linux kernels 2.6.1 and later include +the Lego USB driver in the main tree. For older kernels you'll need +to go get it from legousb.sourceforge.net and compile and install it +yourself; it might easier to just use a serial port connection, if +possible. + +Once you have the USB tower kernel driver installed, set the +environment variable `RCX_PORT' to `usb', using the command + + export RCX_PORT=usb + +if you use the Bourne shell, or + + setenv RCX_PORT usb + +if you use the C shell. You can avoid typing this command each time +you log in by adding it to your .profile under the Bourne shell (or +.bash_profile under Bash) or to .cshrc under the C shell. + +Download Firmware +----------------- + +When you first receive it, the RCX is programmed only with a very +simple operating environment that's only suitable for testing it and +downloading a new set of firmware. So, the first thing you will want +to do is download the standard LEGO firmware. + +If you've used any of the Windows-based LEGO interface software then +you've probably already downloaded the standard firmware and you can +skip this step. If you're not sure, then look at what the RCX display +panel says immediately after you turn it on. If it says 0000, then +the firmware has already been downloaded; if it says something else, +then it probably hasn't been. + +For this step, you'll need the CD that came with your Mindstorms set. +Assuming that the CD is mounted on /cdrom, you can download the +firmware to the RCX using the following command: + + # nqc -firmware /cdrom/firm/firm0309.lgo + +/firm/firm0309.lgo is the name of the firmware file on my CDROM. It +is possible that the name of the firmware file on your own CDROM is +different; if so, substitute its name in the command above. + +While the firmware is downloading a number on the panel of the RCX +will count up from 0 to about 1600. + +If you have trouble downloading the firmware, then consider the +following: + + * Did you symlink the right port to /dev/rcx (or set up USB + correctly)? Make sure that the port isn't in use by any + other device. + + * Is the infrared tower working correctly? If it is, then the + light on it should turn on when the firmware starts + downloading. + + * Is the near/far switch at the base of the infrared tower set + correctly? For near operation the IR tower should be 4-6 + inches from the RCX IR receiver. + + * Is the RCX turned on, with its IR receiver aimed toward the + IR tower, 4-6 inches away? + +Test Compile & Download +----------------------- + +The file test.nqc is included in this package as an example of a +simple NQC program. To compile it and download the resultant program +to the RCX, use the command: + + # nqc -d /usr/doc/nqc/test.nqc + +where nqc is the NQC compiler, -d means to download the result to the +RCX on /dev/rcx, and /usr/doc/nqc/test.nqc is the NQC file to +compile. If all goes well then you should see the message + + Downloading Program: complete + +or similar, from nqc, and NQC will return control to the shell. + +Test Program +------------ + +The program that you just downloaded to the RCX is very simple. It +activates a motor attached to output A and waits for a button attached +to input 1 to be pressed. When the button is pressed, the motor stops +and the program terminates. + +Test the program to verify that it works. If it does, then your RCX +is operating correctly. + +Explore! +-------- + +This package includes a manpage for the nqc program that you can view +with the command `man nqc'. You might also want to visit the NQC +website, which has documentation and examples for NQC. (Previous +versions of this package included these, but this version no longer +does because the new versions do not include a license statement, +making them impossible for Debian to distribute.) + +The NQC website is at: + http://www.baumfamily.org/nqc/ +This site has the NQC documentation in PDF format, the NQC FAQ, links +to related sites, and other NQC resources. + +There is a NQC tutorial on Mark Overmars's site: + http://www.cs.uu.nl/people/markov/lego/ +This tutorial doesn't assume any programming experience. It should be +a good introduction for those to whom the NQC documentation is too +terse. + +Another good LEGO Mindstorms resource is the Lego Mindstorms Internals +page: + http://www.crynwr.com/lego-robotics/ + +Have fun! --- nqc-3.1.r6.orig/debian/changelog +++ nqc-3.1.r6/debian/changelog @@ -0,0 +1,145 @@ +nqc (3.1.r6-1) unstable; urgency=low + + * New upstream release. + + * Apply Makefile fix from + http://launchpadlibrarian.net/8071303/ubuntu_patch.txt. Thanks to + Michael Wales for submitting this fix. + + * Minor packaging changes to upgrade to Debhelper compatibility level 5. + + -- Ben Pfaff Wed, 13 Jun 2007 06:07:50 -0700 + +nqc (2.5.r3-5) unstable; urgency=low + + * compiler/Error.h, compiler/Error.c: Do a more thorough job of tracking + down the real problem with the fData member. I think this will really + fix the FTBFS. Closes: #287812. + + -- Ben Pfaff Fri, 18 Aug 2006 10:27:59 -0700 + +nqc (2.5.r3-4) unstable; urgency=low + + * compiler/Error.h: Change Error's fData member from type `int' to + `intptr_t', to ensure that it has enough room for a pointer. Closes: + #287812. + + -- Ben Pfaff Tue, 15 Aug 2006 14:42:56 -0700 + +nqc (2.5.r3-3) unstable; urgency=low + + * Apply patch from Andreas Jochens to make NQC compile + under GCC 3.4. Closes: #265532. + + -- Ben Pfaff Sat, 4 Sep 2004 14:31:12 -0700 + +nqc (2.5.r3-2) unstable; urgency=low + + * Use /dev/usb/usblegotower0 as default USB device. Closes: #233111. + + -- Ben Pfaff Sat, 21 Feb 2004 19:08:57 -0800 + +nqc (2.5.r3-1) unstable; urgency=low + + * New upstream release. + + * Updated README.Debian and description to include USB instructions. + Please let me know if these are incorrect; I don't have a Mindstorms + set anymore and never had a USB set so I can't test it myself. + + * Added header legousbtower.h into new directory rcxlib/LegoUSB to make + it possible for everything to compile. + + -- Ben Pfaff Sun, 15 Feb 2004 16:31:38 -0800 + +nqc (2.5.r1-1) unstable; urgency=low + + * New upstream release. Closes: #197012. + + -- Ben Pfaff Tue, 17 Jun 2003 22:38:13 -0700 + +nqc (2.3.r1-4) unstable; urgency=low + + * Use /dev/rcx as default serial port. Thanks to Gustavo Laboreiro + for reporting this bug. + + -- Ben Pfaff Sun, 29 Sep 2002 14:22:15 -0700 + +nqc (2.3.r1-3) unstable; urgency=low + + * Change section from electronics to devel. + + -- Ben Pfaff Thu, 11 Oct 2001 12:12:56 -0700 + +nqc (2.3.r1-2) unstable; urgency=low + + * Add Build-Depends: on bison, flex. Closes: #115146. + + -- Ben Pfaff Wed, 10 Oct 2001 18:41:10 -0700 + +nqc (2.3.r1-1) unstable; urgency=low + + * New upstream version. Closes: #106397. + + * Debian package completely redone. + + * No longer includes documentation or examples because there's no + license on the ones available. If someone will get Dave Baum to add a + license then I'll add them back in. + + -- Ben Pfaff Mon, 8 Oct 2001 18:31:58 -0700 + +nqc (2.0.2-2) unstable; closes=50669; urgency=low + + * New upstream documentation. Fixes Bug#50669. Thanks to Jim Studt + for reporting this. + + -- Ben Pfaff Sat, 20 Nov 1999 01:11:32 -0500 + +nqc (2.0.2-1) unstable; urgency=low + + * New upstream version. + + * Migrate to /usr/share/doc. + + -- Ben Pfaff Sat, 13 Nov 1999 12:11:51 -0500 + +nqc (1.3-1) unstable; urgency=low + + * New upstream version. + + -- Ben Pfaff Sat, 10 Jul 1999 15:06:21 -0400 + +nqc (1.0b4-5) unstable; urgency=low + + * Move to section `electronics'. + + -- Ben Pfaff Thu, 28 Jan 1999 21:22:42 -0500 + +nqc (1.0b4-4) unstable; urgency=low + + * Remove -m486 (Bug #31710). + + -- Ben Pfaff Sun, 17 Jan 1999 14:24:12 -0500 + +nqc (1.0b4-3) unstable; urgency=low + + * Include text of MPL in debian/copyright. + + -- Ben Pfaff Mon, 4 Jan 1999 22:05:11 -0500 + +nqc (1.0b4-2) unstable; urgency=low + + * Added HTML documentation. + + * Added example programs. + + -- Ben Pfaff Sun, 27 Dec 1998 10:11:07 -0500 + +nqc (1.0b4-1) unstable; urgency=low + + * New package. + + -- Ben Pfaff Sat, 26 Dec 1998 18:18:39 -0500 + + --- nqc-3.1.r6.orig/debian/dirs +++ nqc-3.1.r6/debian/dirs @@ -0,0 +1,2 @@ +usr/bin +usr/share/man/man1 --- nqc-3.1.r6.orig/debian/rules +++ nqc-3.1.r6/debian/rules @@ -0,0 +1,55 @@ +#!/usr/bin/make -f +# Sample debian/rules that uses debhelper. +# GNU copyright 1997 to 1999 by Joey Hess. + +# Uncomment this to turn on verbose mode. +#export DH_VERBOSE=1 + +configure: configure-stamp +configure-stamp: + dh_testdir + touch configure-stamp + +build: configure-stamp build-stamp +build-stamp: + dh_testdir + $(MAKE) DEFAULT_SERIAL_NAME='"/dev/rcx"' + #/usr/bin/docbook-to-man debian/nqc.sgml > nqc.1 + + touch build-stamp + +clean: + dh_testdir + dh_testroot + rm -f build-stamp configure-stamp + -$(MAKE) clean + rm -f `find . -name \*~` + dh_clean + +# Build architecture-independent files here. +binary-indep: build install +# We have nothing to do by default. + +# Build architecture-dependent files here. +binary-arch: build install + dh_testdir + dh_testroot + dh_clean -k + dh_installdirs + install bin/nqc debian/nqc/usr/bin + dh_installdocs readme.txt scout.txt + dh_installexamples test.nqc + install nqc-man-2.1r1-0.man debian/nqc/usr/share/man/man1/nqc.1 + dh_installchangelogs history.txt + dh_link + dh_strip + dh_compress + dh_fixperms + dh_installdeb + dh_shlibdeps + dh_gencontrol + dh_md5sums + dh_builddeb + +binary: binary-indep binary-arch +.PHONY: build clean binary-indep binary-arch binary install configure --- nqc-3.1.r6.orig/debian/control +++ nqc-3.1.r6/debian/control @@ -0,0 +1,15 @@ +Source: nqc +Section: devel +Priority: extra +Maintainer: Ben Pfaff +Build-Depends: debhelper (>> 5.0.0), bison, flex +Standards-Version: 3.7.2 + +Package: nqc +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends} +Description: Not Quite C compiler for LEGO Mindstorms RCX + The LEGO Mindstorms RCX is a Hitachi microcontroller embedded into a + LEGO brick. This package lets you write programs in a C-like + language and download them to your RCX using the serial or USB + infrared tower included with the RCX. --- nqc-3.1.r6.orig/debian/copyright +++ nqc-3.1.r6/debian/copyright @@ -0,0 +1,389 @@ +This package contains nqc by Dave Baum . + +Packaged for Debian by Ben Pfaff . + +Upstream sources obtained from + http://www.baumfamily.org/nqc/ + +nqc and its manual is covered by the following license: + +/* + * The contents of this file are subject to the Mozilla Public License + * Version 1.0 (the "License"); you may not use this file except in + * compliance with the License. You may obtain a copy of the License at + * http://www.mozilla.org/MPL/ + * + * Software distributed under the License is distributed on an "AS IS" + * basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the + * License for the specific language governing rights and limitations + * under the License. + * + * The Initial Developer of this code is David Baum. + * Portions created by David Baum are Copyright (C) 1998 David Baum. + * All Rights Reserved. + */ + +The text of the MPL is included below: + + + MOZILLA PUBLIC LICENSE + Version 1.0 + + ---------------- + +1. Definitions. + + 1.1. ``Contributor'' means each entity that creates or contributes to + the creation of Modifications. + + 1.2. ``Contributor Version'' means the combination of the Original + Code, prior Modifications used by a Contributor, and the Modifications + made by that particular Contributor. + + 1.3. ``Covered Code'' means the Original Code or Modifications or the + combination of the Original Code and Modifications, in each case + including portions thereof. + + 1.4. ``Electronic Distribution Mechanism'' means a mechanism generally + accepted in the software development community for the electronic + transfer of data. + + 1.5. ``Executable'' means Covered Code in any form other than Source + Code. + + 1.6. ``Initial Developer'' means the individual or entity identified as + the Initial Developer in the Source Code notice required by Exhibit A. + + 1.7. ``Larger Work'' means a work which combines Covered Code or + portions thereof with code not governed by the terms of this License. + + 1.8. ``License'' means this document. + + 1.9. ``Modifications'' means any addition to or deletion from the + substance or structure of either the Original Code or any previous + Modifications. When Covered Code is released as a series of files, a + Modification is: + + A. Any addition to or deletion from the contents of a file + containing Original Code or previous Modifications. + + B. Any new file that contains any part of the Original Code or + previous Modifications. + + 1.10. ``Original Code'' means Source Code of computer software code + which is described in the Source Code notice required by Exhibit A as + Original Code, and which, at the time of its release under this License + is not already Covered Code governed by this License. + + 1.11. ``Source Code'' means the preferred form of the Covered Code for + making modifications to it, including all modules it contains, plus any + associated interface definition files, scripts used to control + compilation and installation of an Executable, or a list of source code + differential comparisons against either the Original Code or another + well known, available Covered Code of the Contributor's choice. The + Source Code can be in a compressed or archival form, provided the + appropriate decompression or de-archiving software is widely available + for no charge. + + 1.12. ``You'' means an individual or a legal entity exercising rights + under, and complying with all of the terms of, this License or a future + version of this License issued under Section 6.1. For legal entities, + ``You'' includes any entity which controls, is controlled by, or is + under common control with You. For purposes of this definition, + ``control'' means (a) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (b) ownership of fifty percent (50%) or more of the + outstanding shares or beneficial ownership of such entity. + +2. Source Code License. + + 2.1. The Initial Developer Grant. + The Initial Developer hereby grants You a world-wide, royalty-free, + non-exclusive license, subject to third party intellectual property + claims: + + (a) to use, reproduce, modify, display, perform, sublicense and + distribute the Original Code (or portions thereof) with or without + Modifications, or as part of a Larger Work; and + + (b) under patents now or hereafter owned or controlled by Initial + Developer, to make, have made, use and sell (``Utilize'') the + Original Code (or portions thereof), but solely to the extent that + any such patent is reasonably necessary to enable You to Utilize + the Original Code (or portions thereof) and not to any greater + extent that may be necessary to Utilize further Modifications or + combinations. + + 2.2. Contributor Grant. + Each Contributor hereby grants You a world-wide, royalty-free, + non-exclusive license, subject to third party intellectual property + claims: + + (a) to use, reproduce, modify, display, perform, sublicense and + distribute the Modifications created by such Contributor (or + portions thereof) either on an unmodified basis, with other + Modifications, as Covered Code or as part of a Larger Work; and + + (b) under patents now or hereafter owned or controlled by + Contributor, to Utilize the Contributor Version (or portions + thereof), but solely to the extent that any such patent is + reasonably necessary to enable You to Utilize the Contributor + Version (or portions thereof), and not to any greater extent that + may be necessary to Utilize further Modifications or combinations. + +3. Distribution Obligations. + + 3.1. Application of License. + The Modifications which You create or to which You contribute are + governed by the terms of this License, including without limitation + Section 2.2. The Source Code version of Covered Code may be distributed + only under the terms of this License or a future version of this + License released under Section 6.1, and You must include a copy of this + License with every copy of the Source Code You distribute. You may not + offer or impose any terms on any Source Code version that alters or + restricts the applicable version of this License or the recipients' + rights hereunder. However, You may include an additional document + offering the additional rights described in Section 3.5. + + 3.2. Availability of Source Code. + Any Modification which You create or to which You contribute must be + made available in Source Code form under the terms of this License + either on the same media as an Executable version or via an accepted + Electronic Distribution Mechanism to anyone to whom you made an + Executable version available; and if made available via Electronic + Distribution Mechanism, must remain available for at least twelve (12) + months after the date it initially became available, or at least six + (6) months after a subsequent version of that particular Modification + has been made available to such recipients. You are responsible for + ensuring that the Source Code version remains available even if the + Electronic Distribution Mechanism is maintained by a third party. + + 3.3. Description of Modifications. + You must cause all Covered Code to which you contribute to contain a + file documenting the changes You made to create that Covered Code and + the date of any change. You must include a prominent statement that the + Modification is derived, directly or indirectly, from Original Code + provided by the Initial Developer and including the name of the Initial + Developer in (a) the Source Code, and (b) in any notice in an + Executable version or related documentation in which You describe the + origin or ownership of the Covered Code. + + 3.4. Intellectual Property Matters + + (a) Third Party Claims. + If You have knowledge that a party claims an intellectual property + right in particular functionality or code (or its utilization + under this License), you must include a text file with the source + code distribution titled ``LEGAL'' which describes the claim and + the party making the claim in sufficient detail that a recipient + will know whom to contact. If you obtain such knowledge after You + make Your Modification available as described in Section 3.2, You + shall promptly modify the LEGAL file in all copies You make + available thereafter and shall take other steps (such as notifying + appropriate mailing lists or newsgroups) reasonably calculated to + inform those who received the Covered Code that new knowledge has + been obtained. + + (b) Contributor APIs. + If Your Modification is an application programming interface and + You own or control patents which are reasonably necessary to + implement that API, you must also include this information in the + LEGAL file. + + 3.5. Required Notices. + You must duplicate the notice in Exhibit A in each file of the Source + Code, and this License in any documentation for the Source Code, where + You describe recipients' rights relating to Covered Code. If You + created one or more Modification(s), You may add your name as a + Contributor to the notice described in Exhibit A. If it is not possible + to put such notice in a particular Source Code file due to its + structure, then you must include such notice in a location (such as a + relevant directory file) where a user would be likely to look for such + a notice. You may choose to offer, and to charge a fee for, warranty, + support, indemnity or liability obligations to one or more recipients + of Covered Code. However, You may do so only on Your own behalf, and + not on behalf of the Initial Developer or any Contributor. You must + make it absolutely clear than any such warranty, support, indemnity or + liability obligation is offered by You alone, and You hereby agree to + indemnify the Initial Developer and every Contributor for any liability + incurred by the Initial Developer or such Contributor as a result of + warranty, support, indemnity or liability terms You offer. + + 3.6. Distribution of Executable Versions. + You may distribute Covered Code in Executable form only if the + requirements of Section 3.1-3.5 have been met for that Covered Code, + and if You include a notice stating that the Source Code version of the + Covered Code is available under the terms of this License, including a + description of how and where You have fulfilled the obligations of + Section 3.2. The notice must be conspicuously included in any notice in + an Executable version, related documentation or collateral in which You + describe recipients' rights relating to the Covered Code. You may + distribute the Executable version of Covered Code under a license of + Your choice, which may contain terms different from this License, + provided that You are in compliance with the terms of this License and + that the license for the Executable version does not attempt to limit + or alter the recipient's rights in the Source Code version from the + rights set forth in this License. If You distribute the Executable + version under a different license You must make it absolutely clear + that any terms which differ from this License are offered by You alone, + not by the Initial Developer or any Contributor. You hereby agree to + indemnify the Initial Developer and every Contributor for any liability + incurred by the Initial Developer or such Contributor as a result of + any such terms You offer. + + 3.7. Larger Works. + You may create a Larger Work by combining Covered Code with other code + not governed by the terms of this License and distribute the Larger + Work as a single product. In such a case, You must make sure the + requirements of this License are fulfilled for the Covered Code. + +4. Inability to Comply Due to Statute or Regulation. + + If it is impossible for You to comply with any of the terms of this + License with respect to some or all of the Covered Code due to statute + or regulation then You must: (a) comply with the terms of this License + to the maximum extent possible; and (b) describe the limitations and + the code they affect. Such description must be included in the LEGAL + file described in Section 3.4 and must be included with all + distributions of the Source Code. Except to the extent prohibited by + statute or regulation, such description must be sufficiently detailed + for a recipient of ordinary skill to be able to understand it. + +5. Application of this License. + + This License applies to code to which the Initial Developer has + attached the notice in Exhibit A, and to related Covered Code. + +6. Versions of the License. + + 6.1. New Versions. + Netscape Communications Corporation (``Netscape'') may publish revised + and/or new versions of the License from time to time. Each version will + be given a distinguishing version number. + + 6.2. Effect of New Versions. + Once Covered Code has been published under a particular version of the + License, You may always continue to use it under the terms of that + version. You may also choose to use such Covered Code under the terms + of any subsequent version of the License published by Netscape. No one + other than Netscape has the right to modify the terms applicable to + Covered Code created under this License. + + 6.3. Derivative Works. + If you create or use a modified version of this License (which you may + only do in order to apply it to code which is not already Covered Code + governed by this License), you must (a) rename Your license so that the + phrases ``Mozilla'', ``MOZILLAPL'', ``MOZPL'', ``Netscape'', ``NPL'' or + any confusingly similar phrase do not appear anywhere in your license + and (b) otherwise make it clear that your version of the license + contains terms which differ from the Mozilla Public License and + Netscape Public License. (Filling in the name of the Initial Developer, + Original Code or Contributor in the notice described in Exhibit A shall + not of themselves be deemed to be modifications of this License.) + +7. DISCLAIMER OF WARRANTY. + + COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN ``AS IS'' BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, + WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF + DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. + THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE + IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE + COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF + ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. + +8. TERMINATION. + + This License and the rights granted hereunder will terminate + automatically if You fail to comply with terms herein and fail to cure + such breach within 30 days of becoming aware of the breach. All + sublicenses to the Covered Code which are properly granted shall + survive any termination of this License. Provisions which, by their + nature, must remain in effect beyond the termination of this License + shall survive. + +9. LIMITATION OF LIABILITY. + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT + (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE INITIAL + DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, + OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO YOU OR ANY OTHER + PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES + OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF + GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND + ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE + BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF + LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY + RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW + PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE + EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THAT + EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. + +10. U.S. GOVERNMENT END USERS. + + The Covered Code is a ``commercial item,'' as that term is defined in + 48 C.F.R. 2.101 (Oct. 1995), consisting of ``commercial computer + software'' and ``commercial computer software documentation,'' as such + terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 + C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), + all U.S. Government End Users acquire Covered Code with only those + rights set forth herein. + +11. MISCELLANEOUS. + + This License represents the complete agreement concerning subject + matter hereof. If any provision of this License is held to be + unenforceable, such provision shall be reformed only to the extent + necessary to make it enforceable. This License shall be governed by + California law provisions (except to the extent applicable law, if any, + provides otherwise), excluding its conflict-of-law provisions. With + respect to disputes in which at least one party is a citizen of, or an + entity chartered or registered to do business in, the United States of + America: (a) unless otherwise agreed in writing, all disputes relating + to this License (excepting any dispute relating to intellectual + property rights) shall be subject to final and binding arbitration, + with the losing party paying all costs of arbitration; (b) any + arbitration relating to this Agreement shall be held in Santa Clara + County, California, under the auspices of JAMS/EndDispute; and (c) any + litigation relating to this Agreement shall be subject to the + jurisdiction of the Federal Courts of the Northern District of + California, with venue lying in Santa Clara County, California, with + the losing party responsible for costs, including without limitation, + court costs and reasonable attorneys fees and expenses. The application + of the United Nations Convention on Contracts for the International + Sale of Goods is expressly excluded. Any law or regulation which + provides that the language of a contract shall be construed against the + drafter shall not apply to this License. + +12. RESPONSIBILITY FOR CLAIMS. + + Except in cases where another Contributor has failed to comply with + Section 3.4, You are responsible for damages arising, directly or + indirectly, out of Your utilization of rights under this License, based + on the number of copies of Covered Code you made available, the + revenues you received from utilizing such rights, and other relevant + factors. You agree to work with affected parties to distribute + responsibility on an equitable basis. + +EXHIBIT A. + + ``The contents of this file are subject to the Mozilla Public License + Version 1.0 (the "License"); you may not use this file except in + compliance with the License. You may obtain a copy of the License at + http://www.mozilla.org/MPL/ + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the + License for the specific language governing rights and limitations + under the License. + + The Original Code is ______________________________________. + + The Initial Developer of the Original Code is ________________________. + Portions created by ______________________ are Copyright (C) ______ + _______________________. All Rights Reserved. + + Contributor(s): ______________________________________.'' + --- nqc-3.1.r6.orig/debian/compat +++ nqc-3.1.r6/debian/compat @@ -0,0 +1 @@ +5