Front page | perl.perl5.porters |
Postings from June 2006
Adam Kennedy wrote: > > 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. Yes, but why do you want the perl core to include the minimal subset of libwin32 modules that is required to install other CPAN modules on Win32, when, in fact, anyone on Win32 is really going to need all of libwin32 anyway? As I've said twice now, I've never heard of anyone on Win32 using perl without libwin32 installed. Yves listed half a dozen Win32 modules that are required for doing just about anything on Win32, all of which are in libwin32, which just confirms how essential it is. As I see it, all people have to do is: - install perl - install libwin32 and they're off. Both of these distributions build out-of-the-box using MinGW + dmake (which are free and only small downloads) and having installed them you're now able to build any other CPAN modules you like and do useful things on Win32. What's the problem? You're suggesting that people should just do: - install perl (including Win32API::File) so that they're able to build other CPAN modules. That's true, but they still can't do all sorts of Win32 things, so they still need libwin32 anyway, in which case what was the point of Win32API::File being in the core? Anyway, what is Win32API::File required for? It isn't required to build every CPAN module, because libwin32 itself builds fine with an unadulterated core perl. ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.Thread Previous | Thread Next