John R. Jackson ([EMAIL PROTECTED]):
>>How about an amadmin command like 'configure-options' that allows you >>to do something like this when upgrading: >> >> ./configure `amadmin configure-options` > That would be almost impossible. Amanda does not have that much control > over ./configure. You would need to know all the args that went in to > ./configure so they could be saved away, but that would require changes > to autoconf (not Amanda). Well, each args that went into ./configure has some effect on the code. So the code that it affects can add the appropriate arg to a common string. I honestly know nothing about autoconf, but I do know that the PHP installation does this. Look at any page with phpinfo() on it and right at the top is the configure string. It's *very* helpful when upgrading a server. > An alternative is to create a file named config.local. If that exists, > it is sourced into ./configure (that's standard autoconf behavior). > So you can do things like this: > with_user=amanda > with_group=amanda > with_tcpportrange=2000,2040 > Just keep this file around and you'll know what you used the last time. Right, but that's an extra step in the install process. Maybe 'make install' should but config.local somewhere helpful (like /var/amanda?) and the docs can mention this technique for upgrading. But it's still not as clean as the previous suggestion. I'm just thinking usability here. Computers are capable of being smart so they should be. :-) -- Jeremy Wadsack Wadsack-Allen Digital Group
