Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

rurban (7989)

rurban
  reversethis-{ta.yar-x} {ta} {nabrur}
http://rurban.xarch.at/

cygwin maintainer for perl, parrot, clisp, postgresql, ... and some perl modules (perl-libwin32, perl-Win32-GUI). Has also some hairy CPAN packages: B::C, B::Generate, C::DynaLib, B::Debugger ...

Journal of rurban (7989)

Saturday January 05, 2008
07:52 PM

cygwin perl updated to 5.10.0-2, libwin32 and Win32::GUI

[ #35303 ]

The cygwin packages for perl-5.10.0-2 and the cygwin modules perl-libwin32-0.28-1 and perl-Win32-GUI-1.05-2 have been updated. Still experimental until all other cygwin perl modules are also updated to 5.10.

What changed from 5.10.0-1 to -2?
@INC has now no duplicate site_perl and vendor_perl entries which came with the new _stem vars and a proper inc_version_list. Stupid.

To add /usr/lib/perl5/site_perl/5.8, without the archlib to @INC I patched perl.c to omit the archlib from otherlibdirs. If someone wants the archlib he should add it explictly to otherlibdirs.

Changed @INC, the include path,
from
    @INC: /usr/lib/perl5/5.10/cygwin /usr/lib/perl5/5.10 /usr/lib/perl5/site_perl/5.10/cygwin /usr/lib/perl5/site_perl/5.10 /usr/lib/perl5/site_perl/5.10/cygwin /usr/lib/perl5/site_perl/5.10 /usr/lib/perl5/vendor_perl/5.10/cygwin /usr/lib/perl5/vendor_perl/5.10 /usr/lib/perl5/vendor_perl/5.10/cygwin /usr/lib/perl5/vendor_perl/5.10
        .
to
    @INC: /usr/lib/perl5/5.10/cygwin /usr/lib/perl5/5.10 /usr/lib/perl5/site_perl/5.10/cygwin /usr/lib/perl5/site_perl/5.10 /usr/lib/perl5/vendor_perl/5.10/cygwin /usr/lib/perl5/vendor_perl/5.10 /usr/lib/perl5/site_perl/5.8
        .

See the cygwin announce:
http://cygwin.com/ml/cygwin/2008-01/ (not yet there)
and the vendor patches at
http://rurban.xarch.at/software/cygwin/release/perl/

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.