|
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 1 September 2016. |
|||
|
01:46
ugexe joined
06:22
domidumont joined
06:28
domidumont joined
08:16
domidumont joined
11:25
domidumont joined
12:39
domidumont joined
14:12
ugexe joined
14:41
ugexe joined
15:16
domidumont joined
16:08
ugexe joined
|
|||
| ugexe | I could figure this out myself but: Lets say someone installs HTTP::UserAgent along with the optional IO::Socket::SSL (which gets loaded in HTTP::UserAgent via `try require ::("IO::Socket::SSL")`). IO::Socket::SSL also gets precompiled during its installation. If someone uninstalls IO::Socket::SSL the precompilation files remain. Can these precompile'd leftovers then cause unexpected behavior, such | 16:53 | |
| as HTTP::UserAgent still using IO::Socket::SSL's precomp files? | |||
| i.e. should precomp files be uninstalled as well? | 16:54 | ||
| afterwards you'd probably have to re-precompile whatever was precompiled against those, but we've known this would need to happen | 16:58 | ||
| DrForr | Speaking of precompiling, an update in the last month seems to have cured the issue I had with needing to nuke precompilled files due to a stale method cache (or whatever it was.) | 17:15 | |
| nine | ugexe: no | 17:21 | |
| We only load precomp files of modules we actually found somewhere. Otherwise we wouldn't even know what name those precomp files may have | |||
|
17:22
leont joined
17:30
DrForr joined
17:32
mst joined
|
|||
| nine | DrForr: maybe by commit 848add944fe6de9090f0abc3b17e9a3a8e2cc42b | 17:32 | |
|
17:33
mst joined
17:35
mst joined
21:01
edehont joined
23:41
TimToady joined
|
|||