> > 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` (JS): it installs a new compiler for each project. I can't imagine how this approach could work with tools like DrRacket.
I know this touches on a reason why PLaneT had issues, but I don't > understand how this is a problem. If two versions of the same package are > in different locations on a filesystem and the module resolver can somehow > distinguish the two using collection paths, then how else do they collide? IIUC, `npm` solves this problem by doing exactly this, but it is pretty naive. A solver based approach can be more optimized: http://www.well-typed.com/blog/2015/03/qualified-goals/. -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CADcuegtP%2BKEDz4rPQV6uU%2B2yMofizwe12Tb0MX1B24zWGjHE-w%40mail.gmail.com.
