public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Reini Urban <rurban@x-ray.at>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] Test update: perl-5.14.2-1, please update your dependent packages
Date: Fri, 27 Apr 2012 07:26:00 -0000	[thread overview]
Message-ID: <announce.CAHiT=DHDqoZZj=c9wiDpnAnK3pYQ5-Du_Bkd6_3+F7fYHEtPWg@mail.gmail.com> (raw)

perl has been updated to 5.14.2-1 as test in the Experimental section.

It looks pretty stable to me when I tested it in the last 2 weeks.

This is to build the 102 (!) dependent packages. I hope the
dependencies can be done
in the next month. Please upload them as test. I'll make the big
switch then by myself
when most packages are updated.

I added a new subpackage perl_vendor which includes all formerly
shipped vendor_perl modules,
which are mainly required to build and test and report test results of
other CPAN modules.

I also added a new subpackage perl_debuginfo which includes stripped
debug symbols
as in fedora. They might come handy if you want to debug into perl or
perl XS modules.

The archname and some minor internals changed. mymalloc is gone.
threads are still unstable. cc is gcc-4.
There is a new Cygwin::sync_winenv function.
The old 5.10 and 5.8 non-arch module paths are kept in @INC, so there
is less need to update.


rebase errors still happen, but are much less common than with 5.10.
There's special code in the ExtUtils::MakeMaker installer to re-use previous
image base addresses on cpan updated dll's.
With a full cpan re-install I got 2 rebase problems. Try to close
bigger dll hogs such the
MS Internet Explorer or SQL Server when doing cpan updates.

I've got some problems with perl-Win32-GUI, but I've got more problems
with perl 5.16 (to be)
than with 5.14, so 5.14 it will be for the time being, at least until
5.16.1 will come out.
5.16.0 looked better in theory than in practise.

In theory I could support parallel perl packages, perl510 and perl514
(or perl516),
but I doubt that other packagers want to support double packages and
rename all their names.
The clashes can be solved via alternatives. manpages and scripts only
for the latest.

Update recommendations from 5.10:
------------------------------------------------

Since 5.14 is not installed in parallel to 5.10 (it is possible, but not
with this package), all your old 5.10 binary modules will need to be
reinstalled for 5.14.

BEFORE INSTALLATION of this 5.14
# get the list of installed 5.8 modules
$ perl -MExtUtils::Installed \
   -e'print join("\n", new ExtUtils::Installed->modules)' > module.list

AFTER INSTALLATION of this 5.14
# install all previous modules for 5.10
$ cpan `cat module.list`

-- 
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2012-04-27  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27  7:26 Reini Urban [this message]
2012-05-03 14:25 ` Achim Gratz
2012-05-03 15:49   ` Reini Urban
2012-05-04  5:33     ` Achim Gratz
2012-05-11 19:00       ` Achim Gratz
2012-05-15 15:06         ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='announce.CAHiT=DHDqoZZj=c9wiDpnAnK3pYQ5-Du_Bkd6_3+F7fYHEtPWg@mail.gmail.com' \
    --to=rurban@x-ray.at \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).