Ken Hornstein <[EMAIL PROTECTED]> writes:
>> I don't think the point was to grab code out of CVS. I think the point
>> was to get it into the OpenAFS CVS tree so that it would be a part of
>> the next OpenAFS release (and future releases), rather than having the
>> kit be a separate entity. Also, if the kit were a part of OpenAFS,
>> then if/when rxkad3 gets implemented, aklog can be changed to work
>> right along side :)
> That would be cool; I think that the kit should still be seperate for
> a little while for people who want to migrate existing realms, but I
> think rolling the necessary bits into OpenAFS to make you be able to
> use V5 "out of the box" would be good.
No fundamental reason why it can't be both; a lot of projects do both
joint and separate releases out of the same repository.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel
