Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-release, 2016-02-05

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:48 ilbot3 joined #perl6-release
02:48 Topic for #perl6-release is now »r̈« - Discussions about Perl 6 and Rakudo release strategies - http://irclog.perlgeek.de/perl6-release/today
03:22 japhb joined #perl6-release
03:36 japhb joined #perl6-release
03:55 japhb joined #perl6-release
05:28 MadcapJake joined #perl6-release
07:33 _Gustaf_ joined #perl6-release
08:11 FROGGS joined #perl6-release
14:30 FROGGS joined #perl6-release
15:16 MadcapJake joined #perl6-release
18:12 nine I think precomp files are actually relocatable. The only absolute paths they contain are the paths to the corresponding source file.
19:45 FROGGS nine: I think it is more about the module search paths
19:45 FROGGS nine: we should try to make nqp relocatable, maybe that's not too hard
19:46 FROGGS because nqp only knows about two or three paths or so
19:48 cognominal joined #perl6-release
20:06 perlpilot joined #perl6-release
20:58 * jnthn wonders if Moar itself is relocatable
21:10 hoelzro it should be, as long as it can find its libs, right?
21:21 jnthn Yeah, which is the bit I'm not sure about ;-)
21:33 hoelzro making it relocatable on Linux wouldn't be too bad, with liberal use of LD_LIBRARY_PATH or chrpath
21:53 perlpilot joined #perl6-release

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary