I read the article you pointed to, but really didn't make much out of it.
Just before giving up, I'd suggest to write an article where you explain the problem, the solution an possibly provide a step-by-step example of how different users might benefit.
Or... just move on to your next project, and good luck!!!
]]>> I'd like to support this in cpan(1)
It's awesome, I'd love to see it!
> I didn't see a definition for "not complicated" that I'd have to support.
Yeah, it is true that we may not say that the spec defines static installable CPAN distributions clearly.
For the time being, I think you can refer to a static builder in Menlo (and github PR). If you have any problems or concerns, let's discuss them in IRC or github issue/PR with toolchain members (especially leont and miyagawa), and improve the spec itself.
]]>Then
* Non-static-install took 28sec
* Static-install took 9sec
That is, static-install is 3x faster. Wow!
]]>Does this relate to the existing `dynamic_config` flag that I added to `Module::Build` (around 15 years ago!)?
http://search.cpan.org/~leont/Module-Build-0.4220/lib/Module/Build/API.pod
I don't quite understand the relationship between `x_static_install` and `dynamic_config` - for instance, the cpan-static spec only mentions `dynamic_config`, and your post above only mentions `x_static_install`.
If it's the same mechanism, it's great to see this getting some support on the build-tools side!
]]>> Does this relate to the existing `dynamic_config` flag that I added to `Module::Build` (around 15 years ago!)?
CPAN::Meta::History::Meta_1_4 says:
dynamic_config:
A boolean flag indicating whether a Build.PL or Makefile.PL (or similar) must be executed when building this distribution, or whether it can be built, tested and installed solely from consulting its metadata file.
On the other hand, current CPAN::Meta::Spec says:
dynamic_config:
A boolean flag indicating whether a Build.PL or Makefile.PL (or similar) must be executed to determine prerequisites.
So it seems that the meaning of dynamic_config has changed, perhaps according to actual uses.
You can refer to miyagawa/cpanminus/pull/467 for why a current static-install implementation in Menlo does not treat dynamic_config as static-install.
Again, I don't think the spec of static-install is fixed, and let's improve the spec and implementation together.
]]>; dist.ini]]>
[StaticInstall]
mode = on