Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support #:name in deps #4313

Open
sorawee opened this issue Jun 19, 2022 · 1 comment
Open

Support #:name in deps #4313

sorawee opened this issue Jun 19, 2022 · 1 comment
Labels
feature request Feature Request

Comments

@sorawee
Copy link
Collaborator

sorawee commented Jun 19, 2022

What version of Racket are you using?
8.5 [cs]

A dependency, which is a package source string, could be a remote URL naming a Git repository. However, the repo name could be invalid package name. Examples include https://github.com/takikawa/pprint.plt and https://github.com/samth/javascript.plt

It would be nice if we can specify:

["https://github.com/takikawa/pprint.plt.git" #:name "pprint"]

as a dependency, and it would essentially run raco pkg install --name pprint https://github.com/takikawa/pprint.plt.git when installing the dependency.

@sorawee sorawee added the feature request Feature Request label Jun 19, 2022
@PanAeon
Copy link

PanAeon commented Nov 24, 2024

Hi I run into this issue recently. I think this is not a feature request, but a proper bug in the design that confuses end users and new package contributors.

Example of the problems this approach creates: catppuccin/drracket#7

I think the proper fix is to priorities #name field from the info.rkt and produce a warning when this field is omitted when raco pkg is invoked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature Request
Projects
None yet
Development

No branches or pull requests

2 participants