[tahoe-dev] Fwd: I put py-zfec on github

[Zooko O'Whielacronx]

Hi Richard:

Thanks for the note!

I'd like to convert the entire zfec history, from darcs, into git, and
update the links inside https://tahoe-lafs.org/trac/zfec to point into
git history instead of darcs history. That's what we've done with
Tahoe-LAFS (https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1964). I'm
not sure if it would be less of a hassle for Brian to give me his
scripts and train me in how to do it, or just to do it himself.

Brian: help?

Regards,

Zooko

On Sat, Jun 8, 2013 at 6:43 AM, Richard Kiss <him at richardkiss.com> wrote:
> Recently I'd been looking for ways to do M of N split on the command-line as
> part of a larger security project. I found py-zfec and found a debian for
> it. But it doesn't install properly, in part because of a dependency on
> pyutil. I understand this dependency probably evolved since tahoe-lafs uses
> pyutil a lot and that's the primary use case for py-zfec. So I took a
> snapshot from darcs, tweaked it to remove the dependency on pyutil and
> pushed it to:
>
> https://github.com/richardkiss/py-zfec
>
> You may want to integrate my changes back to py-zfec. I think py-zfec has
> huge utility in its own right as a stand-alone tool, and making it simpler
> to deploy (and putting it on the github, which is pretty much today's
> SF.net) will go a long ways to increasing awareness of the project.
>
> I'm happy to try to keep things in sync manually, if further changes to
> py-zfec come along.
>
> --
> http://richardkiss.com/
>
>
>
>
> --
> http://richardkiss.com/
>
> Come see me perform! My calendar is at http://laffq.com/richard.kiss
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>