On Tue, Dec 08, 2009 at 04:21:53PM +0100, Jerome Quelin wrote:
> On 09/12/08 13:36 +0100, Moritz Lenz wrote:
> > Yes. Rakudo is released two days after a parrot release, and the Rakudo
> > release works with the installed parrot release (but needs the parrot-devel
> > installation, which previously required `make install-dev` in parrot, and is
> > now part of the default `make install`).
> >
> > This is designed so that distributers can easily ship rakudo if they also
> > ship
> > parrot.
>
> do'h! i was specifically trimming /usr/src from parrot, on behalf that
> this was *probably* not needed.
>
> i just updated the spec file to ship them, and i'll now package & submit
> rakudo on mandriva. however, i'd like to know if this scheme (relying on
> parrot sources being avalable somewhere) will last,
I don't understand why the sources need to be available. Last I checked this
works:
cd parrot
perl Configure.pl --prefix=/some/path/
make install
cd ..
rm -rf parrot
cd rakudo
perl Configure.pl --parrot-config=/some/path/bin/parrot_config
make install
cd ..
rm -rf rakudo
/some/path/bin/perl6 -e 'say "hi"'
So according to my understanding, Rakudo requires a full parrot to be installed
('make install', not just 'make install-bin' or so), but not the parrot source
tree.
Did I miss something? Or does that not work anymore?
Cheers,
Moritz
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
