Re: [racket-users] locally linked package name doesn't match info collection name

There was a `pkg-name` info.rkt item added in 20672cd , but it only seems to be used by `make-dirs-catalog`

Re: [racket-users] locally linked package name doesn't match info collection name

For that, I recommend "Open require path" in the File menu in DrRacket. Sam On Wed, Sep 9, 2020, 9:09 PM Shriram Krishnamurthi wrote: > I'm curious why the Package Manager doesn't also show the collection name > (or plural)? Wouldn't I need that to trace backwards? "This program in > #lang foo

Re: [racket-users] locally linked package name doesn't match info collection name

I'm curious why the Package Manager doesn't also show the collection name (or plural)? Wouldn't I need that to trace backwards? "This program in #lang foo is behaving oddly, I wonder what foo's source is" — find the collection in the PM, trace back to the package, locate the source…? -- You recei

Re: [racket-users] locally linked package name doesn't match info collection name

This is all as expected. The package name is mystery-language-uploader, but the collection name is mystery-language. The info.rkt entry controls the latter but not the former [1]. If you're linking it on the command line, you can use a command line option to specify the package name to use. [1] Th

[racket-users] locally linked package name doesn't match info collection name

This is almost certainly intended and/or I may have totally misunderstood the semantics of the info file, but this feels a bit confusing: I have a package on my filesystem in the directory mystery-languages-uploader. The "-uploader" part is a local name that's not intended for public consumptio