X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20090410161203.GA6883@pmichaud.com>
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> <20090410161203 DOT GA6883 AT pmichaud DOT com>
Date:	Fri, 10 Apr 2009 20:05:50 +0200
Message-ID:	<6910a60904101105v667d132ci96c80e150085a795@mail.gmail.com>
Subject:	Re: [PATCH] rakudo Re: Parrot packaging problems
From:	Reini Urban <rurban AT x-ray DOT at>
To:	"Patrick R. Michaud" <pmichaud AT pobox DOT com>
Cc:	Michael Schroeder <mls AT suse DOT de>, parrot-dev AT lists DOT parrot DOT org,
	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

2009/4/10 Patrick R. Michaud <pmichaud AT pobox DOT com>:
> On Fri, Apr 10, 2009 at 11:09:19AM +0200, Reini Urban wrote:
>> leading to /usr/share/doc/rakudo-2009 and not rakudo-2009-03.
>> I might be tempted to use rakudo-200903 as package name.
>
> We can change the releases to be the 200903 form if that's
> much better. =A0But I personally much prefer the 2009-03 form
> ("2009-03" is an ISO standard date form, whereas "200903" isn't).

I also prefer 2009-03 and will try to work around that simple problem.
It's just the docdir anyway.

>> > One question I have though... why exactly do we need a separate
>> > installable_perl6 target? =A0What does the --install option to pbc_to_=
exe
>> > do that is different from a normal pbc_to_exe run?
>>
>> --install links to install_config.o in contrast to parrot_config.o,
>> so we use the config hash from the installed parrot, with the correct
>> library paths.
>
> For some reason that doesn't sound quite right to me. =A0When converting
> rakudo to an executable, the pbc2exe we use should already know
> if it's being run using an installed parrot or some other parrot
> (because pbc2exe is itself a parrot application). =A0So we shouldn't
> have to pass an explicit flag to it -- we should simply get the
> correct perl6 executable based on whatever pbc2exe was run.

We could check if we use /usr/bin/pbc2exe and assume automatically
--install then, yes.

>> 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/rele=
ase/parrot/CYGWIN-PATCHES/rakudo-2009-03-1-check.log.gz
>>
>> I assume 2009-03 is targetting a newer parrot than 1.0.0,
>> which is unfortunate for a quasi perl6-1.0 release.
>
> The 2009-03 release targets parrot 1.0.0. =A0What you're probably
> seeing is that the spectests (which are outside of the release
> tarball) have changed since the release. =A0So, I guess we may want
> to (a) include a copy of the current spectests at the time of the
> release in the tarball (and change the 'make spectest' target
> to use those) or (b) change the Makefile in the release so that it
> always checks out the spectests that were in effect at the time
> of the release.

Ok, I will check out the right git tag around that date and
include the full tests in the release.

--=20
Reini Urban
http://phpwiki.org/              http://murbreak.at/

--
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/

- Raw text -