Re: [OpenAFS-devel] Re: OpenAFS-devel digest, Vol 1 #25 - 13 msgs

[Russ Allbery]

Derrick J Brashear <[EMAIL PROTECTED]> writes:

> We wanted to get something out there for people to play with. Autoconf
> involves breaking the whole world for the duration of the work,
> basically.

Hm.  It might not *have* to.  We managed to avoid that when
autoconfiscating INN, for example.  Sometimes you can use autoconf to
generate a file that defines all the stuff that the legacy code expects,
and then slowly remove the legacy definitions as they're stripped out of
the rest of the code.

But it depends on how the code's structured and how it uses portability
information and I haven't done a thorough inspection of OpenAFS yet to
figure out a good approach.

-- 
Russ Allbery ([EMAIL PROTECTED])             <http://www.eyrie.org/~eagle/>
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel