public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Steven Hartland" <killing@multiplay.co.uk>
To: <cygwin@cygwin.com>,	"Achim Gratz" <Stromeko@nexgo.de>
Subject: Re: perl-5.14.2 switch
Date: Wed, 11 Jul 2012 23:10:00 -0000	[thread overview]
Message-ID: <60B4845A414A4F228982AB4DEAF4D4FE@multiplay.co.uk> (raw)
In-Reply-To: <87a9z6ywvp.fsf@Rainer.invalid>

----- Original Message ----- 
From: "Achim Gratz" 

> Steven Hartland writes:
>> Cool looking forward to it the new update :)
> 
> I don't think that Reini will switch from perl_vendor to unbundled
> module packages, at least not for this release.  I've posted a link to
> my cygport package definitions over in cygwin-apps if you want to
> compile those packages yourself.  If you don't create your own setup.ini
> files, it's probably not much use.  You can always use cpanminus to
> bootstrap LWP to a newer version locally.

Unfortunately the current perl_vendor install is so broken cpan
won't allow you to fix it with simple "install" unless you know
the exact missing modules and just breaks in some very strange
and random ways. Like missing protocol for ftp in LWP

However the perl_vendor was created it resulted in many missing
dependencies. I don't mind a block install via perl_vendor but
each module installed by that option should include all of its
dependencies otherwise its worse than having nothing at all.

We'd already updated Bundle::LWP via CPAN but its the dependencies
of the dependencies which are missing so they didn't get fixed.

Our fix in the end, so others know, was to use:-
force install LWP::Protocol::ftp

This seemed to force all dependencies in the hierarchy to be
rechecked and hence picked up and installed the missing modules.

    Regards
    Steve


--
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-07-11 23:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 18:01 Reini Urban
2012-07-10 20:56 ` Yaakov (Cygwin/X)
2012-07-10 22:36   ` Reini Urban
2012-07-10 23:10     ` Yaakov (Cygwin/X)
2012-07-10 23:52       ` Reini Urban
2012-07-11  2:20         ` Yaakov (Cygwin/X)
2012-07-11  2:31           ` Reini Urban
2012-07-11  3:02             ` Yaakov (Cygwin/X)
2012-07-11  7:31 ` Dr. Volker Zell
2012-07-11  9:53 ` Yaakov (Cygwin/X)
2012-07-11 15:08   ` Reini Urban
2012-07-11 16:27     ` Steven Hartland
2012-07-11 17:01       ` Achim Gratz
2012-07-11 17:45         ` Steven Hartland
2012-07-11 18:30           ` Achim Gratz
2012-07-11 23:10             ` Steven Hartland [this message]
2012-07-12  5:20               ` Achim Gratz
2012-07-12 15:24                 ` Reini Urban
2012-07-12 16:15                   ` Corinna Vinschen
2012-07-12 16:50                     ` Reini Urban
2012-07-12 18:40     ` Yaakov (Cygwin/X)

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=60B4845A414A4F228982AB4DEAF4D4FE@multiplay.co.uk \
    --to=killing@multiplay.co.uk \
    --cc=Stromeko@nexgo.de \
    --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).