Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-03-12

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

All times shown according to UTC.

Time Nick Message
02:48 ilbot3 joined #perl6-toolchain
02:48 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
03:37 ribasushi joined #perl6-toolchain
07:17 perlpilot joined #perl6-toolchain
07:52 domidumont joined #perl6-toolchain
07:57 domidumont joined #perl6-toolchain
08:42 nine ugexe: I wonder if we couldn't just release the lock right after checking if the dist is already installed.
08:43 nine ugexe: CURI is already designed so installation of a dist is only adding new files and not modifying any existing ones.
10:53 domidumont joined #perl6-toolchain
15:41 ugexe is that true for the precompilation portion as well though?
15:42 ugexe like I thought somewhere it just sort of iterated/recursed over everything it needed to precomp until it worked (sometimes doing the same module more than once if its precomp id changes)
15:47 nine Precompilation must be concurency safe on its own anyway as it can be triggered by simply running programs in parallel (like with prove -j8)
15:49 ugexe i see. but its safe because of the file locking right? I'm not sure where the file lock for precomp ends up, but if its at the root of the precomp repo its not *really* doing anything concurrent other than waiting right?
15:50 ugexe e.g. -j8 gives you 1 thread with the precomp file lock, and 7 other threads waiting for it (but safely)
17:26 nine Yes, it right now locks the whole store. Though it should be simple to use more fine grained locking there, i.e. one lock per precompilation file.

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