Bug #21909 for Perl-Dist-Vanilla: Include libwin32 to vanilla perl

Thu Oct 05 04:39:39 2006 kane [...] cpan.org - Ticket created

Subject:

Include libwin32 to vanilla perl

Greetings, many ported modules require specific win32:: libraries to function on windows. Activestate Perl has included libwin32[1] for a long time which makes it easier to have such distributions run 'out of the box'. One such example is IPC::Run, which relies on Win32::Process to work on windows. Even though all the tools are included with vanilla perl to build this module, since it's such a core part of perl interacting with win32, i think it warrants inclusion in the standard build. -- Jos [1] http://search.cpan.org/~jdb/libwin32/

Thu Oct 05 07:22:56 2006 dagolden [...] cpan.org - Correspondence added

Inclusion of libwin32 would be inconsistent with the stated goal of Vanilla Perl, which is to provide a binary perl that is as close as possible to the Perl source. The only additions are generally a small set of upgraded versions of dual CPAN/core modules that have win32-specific fixes and some minimal configuration to get CPAN.pm running out of the box. Inclusion of libwin32 could be a possibility for Strawberry Perl, however, which is Vanilla Perl plus "developer stuff". However, since libwin32 compiles cleanly on Vanilla/Strawberry, listing any necessary modules from it among dependencies should be sufficient for code which depends on it. The other possibility would be to have libwin32 moved into the Perl core.

Thu Oct 05 07:22:58 2006 The RT System itself - Status changed from 'new' to 'open'

Thu Oct 05 07:22:59 2006 dagolden [...] cpan.org - Status changed from 'open' to 'rejected'

Thu Oct 05 08:33:28 2006 kane [...] cpan.org - Correspondence added

Show quoted text

> > <URL: http://rt.cpan.org/Ticket/Display.html?id=21909 > > > Inclusion of libwin32 would be inconsistent with the stated goal of > Vanilla Perl, which is to provide a binary perl that is as close as > possible to the Perl source. The only additions are generally a small > set of upgraded versions of dual CPAN/core modules that have > win32-specific fixes and some minimal configuration to get CPAN.pm > running out of the box.

Well, you're porting it to Win32, not too weird to have Win32 standard modules ported along... Show quoted text

> Inclusion of libwin32 could be a possibility for Strawberry Perl, > however, which is Vanilla Perl plus "developer stuff". However, since > libwin32 compiles cleanly on Vanilla/Strawberry, listing any necessary > modules from it among dependencies should be sufficient for code which > depends on it.

It doesn't actually compile cleanly on my machine (win2003 server, latest vanilla perl). as win32::OLE refuses to compile. See the attached logfile for details -- it looks like 'some issue' with the included mingw headers, but i'm no real windows developer. Furthermore, libwin32 doesn't adhere to the 'standard' installation process, in that it uses nested Makefile.PLs with nested dependencies, which CPAN.pm and CPANPLUS don't pick up on, so it requires quite a bit of massaging. If you have any suggestions, this is of course much appreciated. -- Jos

Download win32.log
application/octet-stream 30.9k

Message body not shown because it is not plain text.

Thu Oct 05 08:33:30 2006 The RT System itself - Status changed from 'rejected' to 'open'

Thu Oct 05 09:57:49 2006 dagolden [...] cpan.org - Correspondence added

From:

DAGOLDEN [...] cpan.org

On Thu Oct 05 08:33:28 2006, KANE wrote: Show quoted text

> Well, you're porting it to Win32, not too weird to have Win32 standard > modules > ported along...

We're not porting it -- we're just packaging it. All the porting is upstream with p5p and individual package maintainers. Ditto for MinGW. libwin32 is "standard" only in the sense that ActiveState includes it by default, it's not part of the Perl core. Moreover, in the last year or so, several libwin32 packages have been split off and released separately because libwin32 had gone stale and they were needed to address critical bugfixes or other windows shortcomings for bleadperl or other modules. (E.g. Win32API::File, Win32API::Registry, Win32::TieRegistry). Show quoted text

> It doesn't actually compile cleanly on my machine (win2003 server, > latest vanilla perl). > as win32::OLE refuses to compile. See the attached logfile for details > -- it looks like > 'some issue' with the included mingw headers, but i'm no real windows > developer.

I suggest posting a bug report about it to the Win32::OLE queue -- many compiler-compatibility issues are being addresed by module maintainers directly. Show quoted text

> Furthermore, libwin32 doesn't adhere to the 'standard' installation > process, in that > it uses nested Makefile.PLs with nested dependencies, which CPAN.pm > and CPANPLUS > don't pick up on, so it requires quite a bit of massaging.

Personally, I'd like to see all of libwin32 broken up into its individual modules and then have a Bundle::libwin32 that would be used to install them collectively.

Wed Feb 28 22:50:56 2007 dagolden [...] cpan.org - Taken