[OpenAFS-devel] tools and additional autoconf options...

[Neulinger, Nathan]

Since we're starting to add other tools - what's the policy/general
consensus on adding support for other afs related tools?

For example, I'd like to add an updated version of the AFS migration kit and
krb5 patch to tools. That would require adding a --with-krb5= option, and
having that piece of the build use krb5.

Would integrating the migration kit tools be acceptable? (Presuming the
licensing isn't a problem that is. Since all the people involved with it are
involved w/ openafs, I'd presume getting that permission wouldn't be an
issue.)

If this is reasonable to do, I'll put together a patch that will at least
get the aklog and other tools built as part of the openafs build, and we can
see about coming up with a set of megapatches to distribute later. (I track
-current w/ mine, so it may not be the best choice.)

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216