That all sounds fine to me.

I'll just take EU:M and ::Win32 for the moment then.

EU:C can sit where it is until I actually have a chance to apply, or
something better takes it.

I may also want to play with CPAN::SQLite a bit (at the moment the way
it populates the database is pretty horrible) but I've got other
priorities first, so I'll revisit at a later time.

Adam K

On Tue, Nov 30, 2010 at 7:33 AM, David Golden <xda...@gmail.com> wrote:
> On Sun, Nov 28, 2010 at 9:36 PM, Adam Kennedy
> <adamkennedybac...@gmail.com> wrote:
>> I'm happy to take over the small and toolchainy bits of Randy's module
>> list, and move them into my repository.
>>
>> ExtUtils::Command
>> ExtUtils::Manifest
>> File::HomeDir::Win32
>>
>> I wouldn't mind doing some stuff to CPAN::SQLite as well, but if one
>> of the CPAN.pm maintainers wants that instead, give it to them.
>
> I'd like to see File::HomeDir::Win32 moved into File::HomeDir if
> possible and rationalized (aliased?) against File::HomeDir::Windows.
>
> I'm OK with EU::C and EU::M going into the open repository, though I
> think given how tightly integrated EU::C is with EU::MM I wonder
> whether it makes more sense to let mst take it over and unify the two
> or at least manage them concurrently.
>
> -- David
>

Reply via email to