locally linked package name doesn't match info collection name

[Shriram Krishnamurthi]

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 consumption, so its info.rkt contains this:

(define collection "mystery-languages")

Sure enough, I am able to use the content of that directory using, e.g.,

#lang mystery-languages/…

However, the Package Manager only shows an entry (in the "Name" column) for "mystery-languages-uploader", not "mystery-languages". (The "Source" column shows the right folder, and the search box under "Currently Installed" does not show any other package of similar name.)

I would have expected the collection setting to cause the Name showing in the Package Manager to be just "mystery-languages", which would also help me understand where that #lang is coming from.

Shriram

[Sam Tobin-Hochstadt]

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] This is necessary, since you need to know the package name in general to find the info.rkt file in the first place. 

Sam

--
You received this message because you are subscribed to the Google Groups "Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/f99c0426-cb6e-478b-a794-dec114f8cef7n%40googlegroups.com.

[Shriram Krishnamurthi]

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…?

[Sam Tobin-Hochstadt]

For that, I recommend "Open require path" in the File menu in DrRacket. 

Sam

[Philip McGrath]

There was a `pkg-name` info.rkt item added in 20672cd, but it only seems to be used by `make-dirs-catalog`. Maybe it should also be used by "raco pkg install" unless "--name" is given explicitly?

-Philip

On Wed, Sep 9, 2020 at 9:09 PM Shriram Krishnamurthi <shr...@gmail.com> 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 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 received this message because you are subscribed to the Google Groups "Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAJUf2yQqHiryeTsn8Az2PqWPbXV2YwLxGxtNPK_UEVJyGPcJpw%40mail.gmail.com.