RE: [Mason-devel] Re: ANNOUNCE: Mason 1.12

2002-08-08 Thread Ian Robertson
If you ax version numbers now, what happens if someone who already has a versioned copy of ApacheHandler installed asks CPAN to upgrade it? Will it conclude that it already has the most up to date version? For that matter, if another CPAN module simply lists H::M::AH as a dependency (as opposed

Re: ANNOUNCE: Mason 1.12

2002-08-03 Thread Lupe Christoph
On Thursday, 2002-08-01 at 18:06:29 -0400, Perrin Harkins wrote: Dave Rolsky wrote: It can, but I'm not sure what to update it to. Frankly, I think CPAN is more at fault here given that _many_ people use CVS for this sort of stuff and this quite normal when using CVS. It's not CPAN, it's

RE: [Mason-devel] Re: ANNOUNCE: Mason 1.12

2002-08-03 Thread Jonathan Swartz
DR == Dave Rolsky [EMAIL PROTECTED] writes: DR See, that's the problem. We're up in the hundreds. Maybe we should've DR started formatting these with '%04d' way back when but that certainly DR wouldn't help now. How 'bout removing Mason 1.05 from CPAN? Or are there too many apps that

Re: ANNOUNCE: Mason 1.12

2002-08-03 Thread David Wheeler
On Saturday, August 3, 2002, at 03:44 AM, Lupe Christoph wrote: Larry was anticipating a long line of Perl 5 versions... (Yes, I know $] is deprecated. But $^V does not print easily. And vector version numbers are not compatible with 5.005 and earlier, so CPAN modules avoid them.) Not only

Re: ANNOUNCE: Mason 1.12

2002-08-01 Thread Dave Rolsky
On 1 Aug 2002, Vivek Khera wrote: Cool... I just updated one system from 1.05 to 1.1201 and cpan says that HTML::Mason::ApacheHandler is now older than the version in 1.05: Package namespace installedlatest in CPAN file HTML::Mason::ApacheHandler 1.242 1.68

Re: ANNOUNCE: Mason 1.12

2002-08-01 Thread David Wheeler
On Thursday, August 1, 2002, at 01:43 PM, Dave Rolsky wrote: It can, but I'm not sure what to update it to. Frankly, I think CPAN is more at fault here given that _many_ people use CVS for this sort of stuff and this quite normal when using CVS. No, CVS is kind-of brain-dead about this. I

Re: ANNOUNCE: Mason 1.12

2002-08-01 Thread Dave Rolsky
On Thu, 1 Aug 2002, David Wheeler wrote: No, CVS is kind-of brain-dead about this. I suggest you use sprintf to properly format the version number with appropriate number of 0s. Although, with those version numbers, it might be a little late. See, that's the problem. We're up in the

[OT] Re: ANNOUNCE: Mason 1.12

2002-08-01 Thread David Wheeler
On Thursday, August 1, 2002, at 02:11 PM, Dave Rolsky wrote: See, that's the problem. We're up in the hundreds. Maybe we should've started formatting these with '%04d' way back when but that certainly wouldn't help now. I've given up on letting CVS set $VERSION, for just this reason. It's

Re: ANNOUNCE: Mason 1.12

2002-08-01 Thread Vivek Khera
DR == Dave Rolsky [EMAIL PROTECTED] writes: DR See, that's the problem. We're up in the hundreds. Maybe we should've DR started formatting these with '%04d' way back when but that certainly DR wouldn't help now. How 'bout removing Mason 1.05 from CPAN? Or are there too many apps that

Re: ANNOUNCE: Mason 1.12

2002-08-01 Thread Perrin Harkins
Dave Rolsky wrote: It can, but I'm not sure what to update it to. Frankly, I think CPAN is more at fault here given that _many_ people use CVS for this sort of stuff and this quite normal when using CVS. This is a common complaint about CPAN.pm, but it's kept this way so far because of

Re: ANNOUNCE: Mason 1.12

2002-07-24 Thread Josh Chamas
Dave Rolsky wrote: This release has a number of important improvements and it is highly recommended that anyone use Mason 1.10 or 1.11 upgrade immediately in order to fix a nasty memory leak in ApacheHandler. 1.12 is also quite a bit faster than previous 1.1x versions. Some quick

ANNOUNCE: Mason 1.12

2002-07-23 Thread Dave Rolsky
This release has a number of important improvements and it is highly recommended that anyone use Mason 1.10 or 1.11 upgrade immediately in order to fix a nasty memory leak in ApacheHandler. 1.12 is also quite a bit faster than previous 1.1x versions. Those folks still using 1.0x or earlier