| Subject: | new feature: avoid packing dual-lifed modules when not necessary |
12:59 < ether> why does App::FatPacker insist on packing dual-lifed modules, if
I haven't specified a minimum version?
13:00 < ether> e.g. I'm getting File::Spec (and all the OS variants) included,
which adds a huge amount of bloat
13:00 <@mst> because you installed the dual lifed module into your site_perl
13:00 < ether> it's *in core*, I don't need it fatpacked
13:00 <@mst> so that's the version your code is running against
13:00 < ether> ah so it doesn't even see that it's also in core, it just sees
"you require File::Spec, and it's in your site_perl, therefore
I'll pack it"
13:01 <@mst> right. it packs "the things that you are actually loading from site
dirs"
13:01 < ether> I can manually prune it of course, which I'm doing, but I'd like
it to be smarter
13:01 <@mst> this is not clever, but it's very predictable
13:01 < ether> maybe that could be achieved with a commandline option
13:01 < ether> "don't take things that are also in core unless you require a
version greater than what core provides"