Download

License

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.

This program is distributed in the hope that it will be useful, but is provided AS IS, WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, and NON-INFRINGEMENT. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to:

	Free Software Foundation, Inc.
	59 Temple Place - Suite 330
	Boston, MA 02111-1307
	USA

IMPORTANT: By downloading, using, modifying, and/or copying any of the software below or in CVS, you agree to be bound by the terms and conditions of the GNU General Public License.

CVS repository

Those desiring the latest ("unstable", "bleeding edge") code may check it out directly from our CVS repository (using anonymous "pserver" access). Note that our CVS repository starts with revision 0.6.

Use the following commands to "checkout" a copy of the hpoj source code from CVS for the first time. If the "cvs login" command prompts you for a password, then simply press the Enter key.

	cvs -d:pserver:anonymous@cvs.hpoj.sourceforge.net:/cvsroot/hpoj login
	cvs -d:pserver:anonymous@cvs.hpoj.sourceforge.net:/cvsroot/hpoj co hpoj

This will create a directory called "hpoj", known as a "sandbox" in CVS terminology, in the current directory and download the hpoj source code tree into it.

To get started with using the hpoj software, refer to the README and doc/index.html files in the package, which are also mirrored on the web. Also be sure to check the Bugs and TODO page for information on known bugs and patches to solve them.

Once you have created the CVS sandbox and checked out the hpoj source tree, you can download updates at any time by CDing into the "hpoj" directory and using either of the following commands:

• "cvs update" -- updates new, modified, or removed files in existing subdirectories
• "cvs update -dP" -- same as "cvs update", but also downloads files in new subdirectories (-d) and "prunes" empty subdirectories (-P).

If one of the "cvs update" commands lists an "M" (merged) or "C" (conflict) code before any files, that means that one way or another you have made a local modification to those files that are under version control. While you are certainly free under the GPL to modify the hpoj code, it's best not to have to maintain your own private fork of the code, especially if you intend to help test the code that's checked into the repository. From the "hpoj" directory, you can use the command "cvs diff -u" to see what local modifications you have made to the code. If you'd like, you can redirect the output of this command to a file and submit it as a patch for consideration to be checked into the "official" codebase. Otherwise, if you don't care about the changes, you can simply delete the affected files and run "cvs update" again to download "fresh" copies.

If the configure script or any of the Makefiles get updated, then be sure to run "make distclean" and re-run the configure script, make, and "make install" to prevent potential build problems.

More information on CVS may be found at the CVS home page or in the "cvs" manual page on your system.

If you choose to use code from CVS, it is strongly recommended that you subscribe to the hpoj-devel mailing list to stay informed about bugs and other developments.

One may also browse the CVS tree, powered by ViewCVS. This allows one to view histories and perform diffs on any file in the package.

SourceForge CVS issues

Due to load issues, SourceForge has temporarily limited availability of anonymous CVS connections until new server hardware is in place. Click here for more information and updated status. In the meantime, if you get a CVS connection error, then try again later, or pick up an unofficial snapshot at http://www.linuxprinting.org/download/cvs-snapshots/.

Note to distribution maintainers

For support reasons, it is recommended that you don't include hpoj CVS code in stable distributions. Although there may be new features or bug fixes in CVS since the last stable release, there are generally new bugs and/or missing documentation updates that need to be addressed before making a new stable release. Individuals are welcome and encouraged to try out the latest CVS code and submit bug reports and other feedback to help us make future stable releases even better. However, support requests regarding old CVS snapshots will generally be answered with "please upgrade to the latest code."

Experimental code

This code is made available for testing and comment but is not yet part of the official hpoj package, or even CVS. Use at your own risk, and please subscribe to the hpoj-devel mailing list mailing list to stay informed of known issues and updates.

• A snapshot of an preliminary attempt to get hpoj working on Darwin and Mac OS X may be found here. Be sure to read the README file first.