id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
171	Multiple improvements to binary release	Stephen Siegel	zirkel	"Today I had George Avrunin download and run the TASS binary release (linux-64).   It all worked, but here are some important improvements that should be made:

1. include examples in binary release.  But get rid of the file EXAMPLES which is for internal use only.   Also each example should come up with a simple Makefile that executes a few simple tass commands on that example.  This is how the users will learn how to use tass.

2. there is a file called tass~ included in the binary release tar archive.   Delete it.

3. more specific instructions are needed in the README file.  Say that the folder can be placed anywhere, but should not be modified.   Say that the executable is the file called tass in the bin directory; it should not be moved, but you can create a symlink to it.   Say that this executable should be put somewhere in your PATH, either by modifying your PATH environment variable, or by creating a symlink from a place already in your PATH to it.  Give an example of how to invoke tass from the command line to verify/compare something.

4. there should be a source distribution that corresponds to each binary release.   The source distribution should follow the same naming conventions as the binary one, except with something like ""src"" added to the name.  These should both be updated at the same time.  Right now the src release is much older and not up to date, and it is named with lower case letters ""tass"" instead of upper case ""TASS"".
"	enhancement	closed	major	Release 1.0	Administration		fixed	release