Re: [racket-users] Package install conflicts on the Racket package catalog

On 5/5/21, Siddhartha Kasivajhula wrote: > Thank you, that helped me understand the issue. I've made the appropriate > changes so hopefully that'll do it. > > This is reminding me that in python package distribution land, you are able > to explicitly indicate which files make it into the package i

Re: [racket-users] Package install conflicts on the Racket package catalog

Ah looking again, I was mistaken -- lib/test/docs breakdown does not require 3 separate repos. I'll need to take a closer look at how that's set up. Still, the ability to be explicit about package sources could be useful, and may provide a simpler alternative. On Wed, May 5, 2021 at 8:06 PM Siddh

Re: [racket-users] Package install conflicts on the Racket package catalog

Thank you, that helped me understand the issue. I've made the appropriate changes so hopefully that'll do it. This is reminding me that in python package distribution land, you are able to explicitly indicate which files make it into the package in a file analogous to info.rkt (setup.py, but also

Re: [racket-users] Package install conflicts on the Racket package catalog

I think the issue is that you should not use "tests/private" as your collection path. You should probably either "tests/my-collection/private" or "my-collection/tests/private" as the name. Robby On Wed, May 5, 2021 at 4:38 PM Siddhartha Kasivajhula wrote: > That makes sense. Is there a recomme

Re: [racket-users] Package install conflicts on the Racket package catalog

That makes sense. Is there a recommended way to exclude test paths from being part of the package modules? I have a `compile-omit-paths` declaration in the info.rkt file. Since this is

Re: [racket-users] Package install conflicts on the Racket package catalog

I think there's two things you're seeing. 1. The results hadn't yet updated for your typed-compose change. I no longer see a conflict here: https://pkg-build.racket-lang.org/ 2. The conflicts page is for _all_ the packages in the whole package catalog. That's why it always mentions mischief. The

Re: [racket-users] Package install conflicts on the Racket package catalog

Hi, I'd like to chime back in and say that renaming manual.rkt to typed-compose.rkt didn't seem to affect much the list of install conflicts for typed-compose. I also get a lot of conflicts with mischief (but not only), even though typed-compose doesn't depend on it, or doesn't even define na

Re: [racket-users] Package install conflicts on the Racket package catalog

Hi, I'd like to report that I'm seeing conflicts being reported on my packages as well. I haven't made recent changes to these packages so the conflicts seem to have appeared spontaneously. Here is one example: https://pkgs.racket-lang.org/package/lazytree Clicking into the "conflicts" results in

[racket-users] Racket v8.1

-- Racket version 8.1 is now available from https://racket-lang.org/ - DrRacket tabs can be dragged, and have new close buttons. - Racket CS supports cross-compilation using `raco exe`. - Racket CS supports Android on 32-b

[racket-users] Having trouble with HtDP design recipe at exercise 213

Greetings, I'm working through HtDP alone and am currently stuck. All the relevant code can be found here: https://gist.github.com/simalaia/d5b50e9a0bd36b89128aecb43de71cf8 As suggested in the book I start with (insert-everywhere/in-all-words) and design a new function with signature 1Stri

[racket-users] Racket News - Issue 49

Hi all, Apologies all for the yatus on Racket News - but we are back. Issue 49 is finally here and packed with lots of Racket goodness: https://racket-news.com/2021/05/racket-news-issue-49.html Enjoy, -- Paulo Matos -- You received this message because you are subscribed to the Google Groups