develooper Front page | perl.perl5.porters | Postings from October 2009

RE: IO-Compress Makefile.PL problem [was: Re: Special-casing IO-Compress as "XS", and Win32]

Thread Previous | Thread Next
From:
Paul Marquess
Date:
October 5, 2009 11:01
Subject:
RE: IO-Compress Makefile.PL problem [was: Re: Special-casing IO-Compress as "XS", and Win32]
Message ID:
029e01ca45e5$d2bb7b90$783272b0$@Marquess@ntlworld.com
From: Andy Dougherty [mailto:doughera@lafayette.edu]
 
> On Sun, 4 Oct 2009, Paul Marquess wrote:
> 
> > > From: Steve Hay [mailto:steve.m.hay@googlemail.com]
> >
> 
> > > But what about people who have, say, 5.10.1 installed, and then
> > > upgrade to 5.10.2 in the same installation directory? They should
> be
> > > backwards-compatible, so that should work without having to start
> over
> > > with a fresh perl installation, but if we switch to the logic above
> > > and revert the corresponding core change to installperl and
> > > win32/FindExt.pm to match then the 5.10.2 files will go into lib
> and
> > > won't be seen because of existing 5.10.1 files already in archlib.
> >
> > Do people actually do that? Any time I ever upgrade, I start from
> scratch
> > and wipe the old one.
> >
> > > I think you're right that it doesn't need to stay in archlib
> > > long-term, but I think it has to stay where it is for 5.10.x.
> >
> > I'm happy to go along with that if in-place upgrades are likely to be
> a
> > problem.
> 
> Yes.  In-place upgrades are supposed to work smoothly, so the 5.10.1
> behaviour should be maintained throughout the 5.10.x series, as long as
> that's not overly burdensome.

OK, thanks.

Paul


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About