On Thu, Feb 19, 2009 at 11:18:37AM -0500, Dustin J. Mitchell wrote:
> On Thu, Feb 19, 2009 at 10:48 AM, stan <stanb AT panix DOT com> wrote:
> > But, if one is already puting amanda in it's own tree, as we are
> > (/opt/amanda) then this just adds another (confusing) directory to the path
> > (EG /opt/amanda/libexec/amanda) `. Is it possible to overide this behavior?
> 
> Yep -- see --without-amlibdir in the ./configure --help output that
> Jean-Louis pasted.
> 

Hmm, I'm having a bad dy. I put:
--without-amlibdir
In my script that runs configure. but i still get:

Build documentation: no
Directories:
  Application: /opt/amanda/libexec/amanda/application
  Configuration: /opt/amanda/etc
  GNU Tar lists: /opt/amanda/var/gnutar-lists
  Perl modules (amperldir): /opt/amanda/lib/perl
  Template and example data files (amdatadir):
  /opt/amanda/share/amanda
  Temporary: /tmp/amanda

I alos put 
--with-amperldir=/opt/amanda/lib/perl
in the same script, and, as you can see it was honored. Also can i change
 /opt/amanda/share/amanda
 to /opt/amanda/share
 somehow?

-- 
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.