Can you take a look at the version of amanda located in rawhide? You will have
to rebuild it with dump installed on your machine since it wasn't on my
buildroot (doh!). Check that out to make sure it works.

Tim

Nope, that doesn't have it either.  The docs suggest what I said before,
that the command must be built in a separate step.  I also noticed that
the step builds a "temporary wrapper script" in tape-src/, which includes
a warning that it won't work if moved out of the build directory.  I'm not
sure what's going on there.

From waht I can tell, the tapetype script is generated so that you can run it
for *machine dependant information*, and it must be run from the source
directory otherwise it will not function properly. Here is a snippet from
examples/amanda.conf in the source:

	"# Define the type of tape you use here, and use it in "tapetype"
	 # above.  Some typical types of tapes are included here.  The tapetype
	 # tells amanda how many MB will fit on the tape, how big the filemarks
	 # are, and how fast the tape device is.

	 # A filemark is the amount of wasted space every time a tape section
	 # ends.  If you run `make tapetype' in tape-src, you'll get a program
	 # that generates tapetype entries, but it is slow as hell, use it only
	 # if you really must and, if you do, make sure you post the data to
	 # the amanda mailing list, so that others can use what you found out
	 # by searching the archives. "

This suggests that you can use it to generate some defines, but is not
completely necessary if it was generated by someone else. FWIW, a make is done
inside the tape-src directory, and the libraries are built and installed
(/usr/lib/libamtape*).

This is why we haven't built the package with this script, we would have to
install the source as part of the regular package in order for the tapetype
script to work. If you have an entry that hasn't been documented on this page:

http://www.cs.columbia.edu/~sdossick/amanda/

Then you may want to go ahead and build amanda by hand if you are concerned
about the tapetype definitions.

Tim

Yes, the point of the utility is to generate machine-dependent information,
but it's not for #defines in source code.  It's for a runtime config file:
/etc/amanda/*/amanda.conf.  It would be nice if one could test one's drive
for inclusion in this file without having to build the whole package from
source.

It looks like the main reason that the script is not relocatable is that
it is looking for some shared libs in particular locations.  I don't see
why the script couldn't be rewritten to invoke the executable correctly
when the package is installed, but that's basically a wish list item.