[OpenAFS] Re: Extract files from /vicepa
Fri, 17 Jan 2014 17:20:00 -0500
On Fri, 2014-01-17 at 14:41 -0600, Andrew Deason wrote:
> On Fri, 17 Jan 2014 19:57:55 +0100
> Stephan Wiesand <email@example.com> wrote:
> > In a perfect world, Andrew would now pick up your CVS repository,
> > merge the improvements into the github one he mentioned, and start
> > submitting the results to gerrit.openafs.org.
> Do you mean under openafs.git, or something else? I plan on looking at
> that CVS repo and putting the changes into git somewhere, but I hadn't
> yet thought that it would go into openafs.
So, part of the problem with just "merging the improvements" is that
that github repository doesn't contain the complete history; it was
created by importing the 1.2 tarball.
It would certainly be possible for someone to merge the changes into
OpenAFS, but I'd rather not. I do not subscribe to the notion that
every AFS-related tool needs to be part of the OpenAFS distribution.
> > I'd love to see the state of the art of this being part of our regular
> > OpenAFS releases. Obviously, there's a real need for these tools.
> > Are there any licensing obstacles?
> No, the licensing seems pretty permissive. I thought there was some
> desire to have some of the simpler tooling separate from OpenAFS itself,
> like some of the other stuff in openafs-contrib. The README text makes
> it pretty clear that at least the original authors wanted that; I
> thought that jhutz and some users might agree with that, as well.
In the case of dumpscan, I _am_ the original author. The code was
originally written prior to the release of OpenAFS, and was intended to
be distributed separately and not depend on AFS. It does contain rx and
com_err dependencies today, but the former is needed only for a feature
that could easily be made optional, and the latter can be satisfied from
In any case, I've been asked to produce a real repository, and will try
to do so soon. At that point, it should be fairly easy to merge in the
changes that are in the openafs-contrib repo, and do a release. In the
meantime, as always, patches are welcome.