I started a Chef cookbook for Parrot :
https://github.com/leto/cookbooks/tree/parrot
Can anybody help me test it? I know I have the package name correct
for Ubuntu/Debian, but I am not sure what they are called on other
OS'es.
Duke
--
Jonathan "Duke" Leto <jona...@leto.net>
Leto Labs LLC
209.691.DUKE // http://labs.leto.net
NOTE: Personal email is only checked twice a day at 10am/2pm PST,
please call/text for time-sensitive matters.
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
> Can anybody help me test it? I know I have the package name correct
> for Ubuntu/Debian, but I am not sure what they are called on other
> OS'es.
On openSUSE it's parrot as well.
Stefan
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
(But note that you need 'parrot-devel' if you want to do language
development.)
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
I am pretty sure 'parrot' subsumed the duties of both 'parrot' and
'parrot-devel' about a year or so ago.
At least that is true for the Debian/Ubuntu ports.
This happened because "make install" and "make install-dev" became the
same thing.
Thanks for taking a look!
Duke
--
Not true for openSUSE.
> This happened because "make install" and "make install-dev" became the
> same thing.
Yes, but the parrot/parrot-devel split has not much to do with
'make install'. It's how the installed files are split into packages.
But I agree that the parrot package is kind of empty, it only
contains the /usr/bin/* files. Thus parrot, parrot-nqp, winxed,...