Suggestion: upgrade and improvement

[ccworld1000]

Suggestion: upgrade and improvement

Each upgrade causes the original module to be downloaded from the network to be lost and needs to be reinstalled.

If there is a little more module dependency, it seems that this is not very reasonable.

If upgraded, the module that is downloaded from the previous version is expected to be retained.

This eliminates the need to reinstall the dependency after each upgrade.

[JJ]

I'm not sure there's an alternative. Since modules are precompiled and installed, I think that's quite necessary. That's a requirement of Rakudo, not rakudo star, far as I can see

[ccworld1000]

In general, this built-in repository is independent of other places, and app deletion is unaffected unless there are significant incompatible versions.

[JJ]

@ccworld1000 still. Modules are not used directly, they are precompiled, so that is why they need to be reinstalled. And I don't think that depends on Rakudo Star, but on Rakudo itself.

[ccworld1000]

That's the design imperfection. If more and more libraries are used, they should be deleted and reinstalled every time they are updated. Less is better, if more?

One of the future programming directions is to call more different libraries

[jnthn]

Modules are not used directly, they are precompiled, so that is why they need to be reinstalled. And I don't think that depends on Rakudo Star, but on Rakudo itself.

Rakudo automatically recompiles existing modules on first usage with a new version of the compiler. I'm doing source builds, but re-install Rakudo multiple times a week without losing installed modules. So it seems the requested feature is possible so far as Rakudo goes.

[ccworld1000]

excellent

[AntonOks]

closing as it's stone-age old an no one seems to work on it...

After the switch to ZEF for the "modules.txt.2 installation, if I get this here right... you could set RAKULIB / RAKUDOLIB to point to something outside your installation dir before running "RSTAR install" now...