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?
-------- Original Message -------- On May 1, 2020, 6:29 AM, Alex Harsanyi wrote: > On Friday, May 1, 2020 at 1:02:04 PM UTC+8, Sage Gerard wrote: > >>> The "project" would be the toplevel folder where the source files for a >>> Racket application (not a package) >> >> Why can it not be a package? I would be very, very interested in finding a >> way to make this work for packages as well. > > If you want this to work for packages as well you will have to deal with the > case where two versions of the same package are required in the same racket > process. E.g. package A depends on packages B and C, B depends on package D > version 1, while C depends on package D version 2. > > This complicates things somewhat. > > Alex. > > -- > 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 [email protected]. > To view this discussion on the web visit > [https://groups.google.com/d/msgid/racket-dev/017572c9-8d38-4899-b4a3-da03acd783ab%40googlegroups.com](https://groups.google.com/d/msgid/racket-dev/017572c9-8d38-4899-b4a3-da03acd783ab%40googlegroups.com?utm_medium=email&utm_source=footer). -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/NZzkkcNDn5c039YNPslLadVIZIjrhOfWnsGrw01nnJOjtjR99LmgcAISiSZQpwEuJyWdntXxxpqLhaVBCMf3sW6ZJwTswvSYMT4fnG_Tt3M%3D%40sagegerard.com.
