|
Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec Set by moderator on 23 November 2016. |
|||
|
02:48
ilbot3 joined
|
|||
| moderator | Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec | ||
|
06:57
domidumont joined
07:03
domidumont joined
08:19
domidumont joined
|
|||
| tbrowder | hi #perl6-toolchain, anyone here? | 11:28 | |
| nine | hi | 11:32 | |
| tbrowder | hi, nine | 11:56 | |
| i'm working on the rakudo star installation trying to make zef the only installer and, so far, am making progress | 11:57 | ||
| nine | You mean our download .tar.gz? | 11:58 | |
| tbrowder | my question is has anyone thought about breaking the whole rakudo installation process into more discrete pieces? | ||
| exactly, the rakudo*star* specifically | |||
| my immediate need is to have a stand-alone package to install rakudo star site-wide, as root, on multiple servers so i have a consistent, easily-updatable, perl6 environment, so that is what i'm working on with the goal of a PR soon | 12:00 | ||
| nine | I wonder why you focus on star for that? | 12:10 | |
| tbrowder | well, i could foccus on the main distro, but folks on #perl6 didn't seem to want a module installer with it. i want zef to be the main installer because panda doesn't seem to be very consistent in how it gets installed and updated. | 12:12 | |
| nine | My approach is to create and maintain RPM packages for rakudo, zef, Inline::Perl5 and whatever else we're gonna end up using. | 12:13 | |
| Already got moarvm, nqp and rakudo. Just need to do it for zef and Inline::Perl5 | 12:14 | ||
| tbrowder | nine, do you make deb packages also? | 12:29 | |
| nine | Nope. Don't have any deb based system. | 12:39 | |
| I'm using the Open Build Service. That supports deb, too. So it should be relatively straight forward for one who needs it. | |||
| tbrowder | nine: i'll check it out--thanks! | 13:47 | |
| nine: are your open build service setup files publicly available? | 13:51 | ||
|
14:36
tadzik joined
|
|||
| tbrowder | nine: even though it's RPM they would be helpful for a new Open Build Service user... | 15:24 | |
| nine | tbrowder: build.opensuse.org/project/show/de...ges:parrot | 15:35 | |
| you'll find the .spec files in the packages | |||
| tbrowder | nine: thanks! | 15:38 | |
|
15:59
FROGGS joined
17:13
b2gills joined
18:07
domidumont joined
19:29
domidumont joined
19:47
domidumont joined
|
|||
| stmuk_ | I don't see much point in replacing panda in star with zef | 20:57 | |
| mst | I was under the impression that most people thought zef was a better approach at this point, and that tadzik had no problem with us kicking his puppy | 21:01 | |
| tadzik | I'm all for Star containing software that's maintained :) | 21:02 | |
| proactively, not reactively | |||
| it's supposed to be a collection of the best modules, and zef is better than panda | |||
| stmuk_ | my main issue with zef is that the search only works if you know exactly what you are searching for | ||
| nine | That ought to be fixable? | 21:03 | |
| tadzik | searching for something you already know seems pretty useless :) | 21:04 | |
| stmuk_ | the whole rakudo-rakudo star thing is too confusing for people anyway | 21:06 | |