On 03/05/2013 12:02 PM, Rob Hoelz wrote:
On 3/5/13 11:44 AM, Patrick R. Michaud wrote:
On Tue, Mar 05, 2013 at 11:13:51AM +0100, Rob Hoelz wrote:
I already have my own package for Arch Linux for Rakudo Star, and I keep
the OS X homebrew package up-to-date as well. I'd like to create an RPM
spe
On Tue, Mar 5, 2013 at 6:07 AM, Patrick R. Michaud wrote:
>
> Same here. I think "something more appropriate" is much more likely to
> arrive with the "go ahead and make" approach than the "hold off" one. :)
>
I agree with Patrick. Experimenting with the packaging now should
flush out the bugs b
On Tue, Mar 05, 2013 at 12:02:01PM +0100, Rob Hoelz wrote:
> On 3/5/13 11:44 AM, Patrick R. Michaud wrote:
> > It may also be worth noting/reminding that Rakudo Star has never been
> > intended to be the "only" or even "primary" module collection, it's just
> > one of the first. It could make good
On 3/5/13 11:44 AM, Patrick R. Michaud wrote:
> On Tue, Mar 05, 2013 at 11:13:51AM +0100, Rob Hoelz wrote:
>> I already have my own package for Arch Linux for Rakudo Star, and I keep
>> the OS X homebrew package up-to-date as well. I'd like to create an RPM
>> spec file and a DEB spec file as well
On Tue, Mar 05, 2013 at 11:13:51AM +0100, Rob Hoelz wrote:
> I already have my own package for Arch Linux for Rakudo Star, and I keep
> the OS X homebrew package up-to-date as well. I'd like to create an RPM
> spec file and a DEB spec file as well. I have two questions:
>
> 1) Do these spec file
Hi everyone,
There was some discussion on #perl6 yesterday on what requirements are
necessary for Perl 6 to be considered "production ready", and moritz++
made a quick list (https://gist.github.com/moritz/5082925) of the top of
his head including deployment in major free OSes. This is one area
wh
