Taking over Crypt::Rijndael

brian_d_foy on 2006-11-01T09:30:25

I have a use for Crypt::Rijndael, and it appears the author has disappeared (for the last several years). Unless anyone complains, I'm going to take over the module, apply the outstanding patches, etc.

---

Re: Taking over Crypt::Rijndael

fireartist on 2006-11-01T12:32:51

Earlier this year I contacted the author and he said he wasn't using perl anymore and was happy for me to take it over. Adam Kennedy gave me co-maint on it, but to my shame I have yet to make a release.
If you've got the time to do it, please do!
I had been planning on adding it to Adam's shared svn repository, but however you want to do it is fine.
The specific fix I wanted was to get it to work with VanillaPerl. I'll check whether I posted it to RT, and if not, I'll post the patch.

Re: Taking over Crypt::Rijndael

Alias on 2006-11-01T13:25:27

So how would you prefer to do this Brian?

Take it over entirely, or do you want me to chuck it in my svn (since so many people already have commit) where multiple people can hack on it, and you can release from there...

Thoughts?

Re: Taking over Crypt::Rijndael

brian_d_foy on 2006-11-01T21:18:47

If I take it over, I'll use my own repository. I know that in your svn, people can commit to it, but I also know that they haven't.

If fireartist or anyone else wants to maintain it, that's fine, but then they have to actually maintain it.

Re: Taking over Crypt::Rijndael

fireartist on 2006-11-02T08:46:39

To be honest, I'd rather you maintain it.
My reason for patching it was just to get it working with VanillaPerl, but I haven't even used Windows in months now, which is why it slipped off my TODO list.
My knowledge of xs is also very basic.

Re: Taking over Crypt::Rijndael

brian_d_foy on 2006-11-02T09:27:08

We could fight over who has less XS knowledge :)