>
> There are basically two approaches in wide use here, depending on
> whether the underlying system was developed after this kind of package
> management approach became popular (npm, cargo, stack) or before
> (virtualenv for python and others).
>
>
`stack` (Haskell) is a bit different from `npm`
Thanks for the link. Is there a way to use the solver-based approach that's
easier than involving a tethered installation or a custom launcher? On my end
it looks like any different approach to packages would need a different module
name resolver too.
~slg
‐‐‐ Original Message ‐‐‐
On T
FWIW:
Changing the search path for modules isn't just about changing the
`current-module-name-resolver` parameter. Paths and search rules end up
getting used in subtly different ways by different tools, such as
`racket` versus `raco setup` versus `raco exe`. The module name
resolver is more of a h
Thanks for this, it really helps.
I'm not sure what improvements can be made that A) wouldn't repeat the problems
encountered in PLaneT and B) gives users an "easy" way to deal with breaking
changes in collection names beyond what the Package Management FAQ suggests.
I remember Sam mentioning `
At Thu, 21 May 2020 15:39:30 +, Sage Gerard wrote:
> I'm not sure what improvements can be made that A) wouldn't repeat the
> problems encountered in PLaneT and B) gives users an "easy" way to deal with
> breaking changes in collection names beyond what the Package Management FAQ
> suggests.
