Front page | perl.perl5.porters |
Postings from June 2006
Steve Hay wrote: > Adam Kennedy wrote: >> Steve Hay wrote: >>> Adam Kennedy wrote: >>>>> I've personally never heard of anyone trying to use perl on Win32 >>>>> without having libwin32 installed anyway, so including it in the >>>>> core wouldn't change Win32 users' lives that much. It isn't hard >>>>> to install, being all in one bundle, and for those who can't manage >>>>> there's always ActivePerl. >>>> >>>> *waves* >>>> >>>> Might I suggest installing Vanilla to experience what it's like, if >>>> you have a spare hour. >>> >>> To experience what what is like? Do you mean "experience what >>> installing libwin32 is like", or "experience what Vanilla Perl is like"? >> >> To experience what it's like having core Perl but not having libwin32 >> and none of the other Win32 modules. > > Oh, I see. Well, I've never tried that and I can't see why I'd want to. Because... Steve Hay wrote: > I've been trying to look at all the Win32 patches that come in > for quite a while now and I don't recall having overruled or ignored > any, except possibly suggestions for including new (Win32) modules > into the core, which I don't feel I could unilaterally do without > support from others. And thus, now you have a vehicle for seeing WHICH Win32 modules are truly necesary in the core and could be merged, and which aren't and can be rejected. So far, I think that the problems with installing modules in the CURRENT codebase certainly justifies Win32API::File. Nothing else yet is that obvious, unless we were to consider File::HomeDir to be desirable in the core, but I don't consider it ready for the variety of platforms it would need to handle yet. But let's take this to a different thread... Adam K