Skip Menu |

This queue is for tickets about the Class-MOP CPAN distribution.

Report information
The Basics
Id: 58037
Status: rejected
Priority: 0/
Queue: Class-MOP
People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: 1.02
Fixed in: (no value)

History Show all quoted text
  Wed Jun 02 01:38:35 2010 SREZIC [...] cpan.org - Ticket created
Subject: Automatic Moose upgrade
I think it should be easily possible to automatically upgrade Moose if Class::MOP's Makefile.PL detects that otherwise Moose will be broken, just by dynamically add a "requires Moose => ..." line if necessary. Regards, Slaven
  Wed Jun 02 01:44:42 2010 DOY [...] cpan.org - Correspondence added
Nope... requires are resolved before the requiring package is built, so this would just cause a circular dependency (Class::MOP would require a newer version of Moose, which would itself require the newer version of Class::MOP, etc). This needs more toolchain support before this will be possible.
  Wed Jun 02 01:44:43 2010 The RT System itself - Status changed from 'new' to 'open'
  Wed Jun 02 01:44:43 2010 DOY [...] cpan.org - Status changed from 'open' to 'resolved'
  Wed Jun 02 01:45:10 2010 autarch [...] urth.org - Correspondence added
Subject: Re: [rt.cpan.org #58037] Automatic Moose upgrade
Date: Wed, 2 Jun 2010 00:45:01 -0500 (CDT)
To: Slaven_Rezic via RT <bug-Class-MOP [...] rt.cpan.org>
From: Dave Rolsky <autarch [...] urth.org>
On Wed, 2 Jun 2010, Slaven_Rezic via RT wrote: Show quoted text
> Wed Jun 02 01:38:35 2010: Request 58037 was acted upon. > Transaction: Ticket created by SREZIC > Queue: Class-MOP > Subject: Automatic Moose upgrade > Broken in: 1.02 > Severity: Wishlist > Owner: Nobody > Requestors: SREZIC@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=58037 > > > > I think it should be easily possible to automatically upgrade Moose if > Class::MOP's Makefile.PL detects that otherwise Moose will be broken, > just by dynamically add a "requires Moose => ..." line if necessary.
And then Moose will require the new CMOP, and we have a circular dependency. -dave /*============================================================ http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) ============================================================*/
  Wed Jun 02 01:45:12 2010 The RT System itself - Status changed from 'resolved' to 'open'
  Wed Jun 02 02:58:10 2010 SREZIC [...] cpan.org - Correspondence added
On 2010-06-02 01:44:42, DOY wrote: Show quoted text
> Nope... requires are resolved before the requiring package is built, so > this would just cause a circular dependency (Class::MOP would require a > newer version of Moose, which would itself require the newer version of > Class::MOP, etc). This needs more toolchain support before this will be > possible.
I think at least CPAN.pm can handle circular dependencies. But I'll first ask Andreas today. Regards, Slaven
  Wed Jun 02 03:53:16 2010 SREZIC [...] cpan.org - Correspondence added
On 2010-06-02 02:58:10, SREZIC wrote: Show quoted text
> On 2010-06-02 01:44:42, DOY wrote:
> > Nope... requires are resolved before the requiring package is built, so > > this would just cause a circular dependency (Class::MOP would require a > > newer version of Moose, which would itself require the newer version of > > Class::MOP, etc). This needs more toolchain support before this will be > > possible.
> > I think at least CPAN.pm can handle circular dependencies. But I'll > first ask Andreas today.
No, unfortunately CPAN.pm does not handle circular dependencies. Regards, Slaven
  Sun Jun 06 10:06:01 2010 DROLSKY [...] cpan.org - Status changed from 'open' to 'rejected'