Opened 16 years ago

Closed 16 years ago

#171 closed enhancement (fixed)

Multiple improvements to binary release

Reported by: Stephen Siegel Owned by: zirkel
Priority: major Milestone: Release 1.0
Component: Administration Version:
Keywords: release Cc:

Description

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.
  1. there is a file called tass~ included in the binary release tar archive. Delete it.
  1. 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.
  1. 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".

Change History (6)

comment:1 by zirkel, 16 years ago

Owner: set to zirkel
Status: newaccepted

comment:2 by Stephen Siegel, 16 years ago

Also, could we change the file suffixes from ".tar.gz" to just ".tgz". It is more concise and standard.

comment:3 by Stephen Siegel, 16 years ago

And: let's add a 32-bit linux version for the poor folks out here (like Lou Rossi) who are still in the 32-bit world.

comment:4 by zirkel, 16 years ago

Should the Makefiles use the absolute path to tass (../../bin/tass) or assume the user has it in their PATH?

Also, is it sufficient to have a verify target that verifies the spec and a compare target?

comment:5 by zirkel, 16 years ago

Is it ok for the Makefiles to assume tass is in the PATH?

comment:6 by zirkel, 16 years ago

Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.