X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_05,RDNS_DYNAMIC X-Spam-Check-By: sourceware.org Message-ID: <49DF13A6.6000502@jnthn.net> Date: Fri, 10 Apr 2009 11:38:46 +0200 From: Jonathan Worthington User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Reini Urban CC: "Patrick R. Michaud" , cygwin AT cygwin DOT com, parrot-dev AT lists DOT parrot DOT org Subject: Re: [PATCH] rakudo Re: Parrot packaging problems References: <20090408101541 DOT GA6404 AT suse DOT de> <49DCEC65 DOT 4000400 AT x-ray DOT at> <20090409102012 DOT GD1506 AT suse DOT de> <49DE45E6 DOT 5030508 AT x-ray DOT at> <20090409212923 DOT GA10858 AT pmichaud DOT com> <6910a60904100209l54b238dbuf56b10251364fc99 AT mail DOT gmail DOT com> In-Reply-To: <6910a60904100209l54b238dbuf56b10251364fc99@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reini Urban wrote: > I also get lots of spectest failures of 2009-03 with parrot-1.0.0. > See http://code.google.com/p/cygwin-rurban/source/browse/#svn/trunk/release/parrot/CYGWIN-PATCHES/rakudo-2009-03-1-check.log.gz > > I assume 2009-03 is targetting a newer parrot than 1.0.0, > Correct. 2009-02 was the release that came after Parrot 1.0.0 and targeted it. > which is unfortunate for a quasi perl6-1.0 release. > I think you're the first person I've heard refer to it as such... Parrot development very much continues beyond Parrot 1.0, and Rakudo releases beyond the 2009-02 one will depend on those - and forthcoming - changes. Thanks, Jonathan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/