racket / racket/drracket

Update button doesn't appear to pass the same --deps argument as Do What I Mean

Open
#710 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

I ran into this when updating the lsl package from commit a4ca8306 to commit f4edfabb. Between these commits, a new dependency was added to lsl-lib (which is a dependency of lsl). I went to the "Installed Packages" tab in the package manager, highlighted lsl and lsl-lib, and clicked "Update". This failed with the following:

drracket update: missing dependencies;
 specify `--deps search-auto' to install them, or
 specify `--deps search-ask' to be asked about installing them
  for package: lsl-lib
  missing packages:
   t-test

When I instead typed lsl in the "Do What I Mean" box and pressed Enter, the update completed successfully. It was not clear to me how to get the equivalent raco command for the "Update" button, but "Do What I Mean" does the following:

raco pkg update --deps search-auto --scope user lsl

I would have expected the Update button to either show a pop-up asking if I wanted to install the new dependencies, or just install them for me automatically (like "Do What I Mean" did).

DrRacket version 8.15, installed via the Arch Linux repo.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in DrRacket's Installed Packages tab by updating lsl and lsl-lib after the dependency change. Compare the command used by the Update button with the documented Do What I Mean command, raco pkg update --deps search-auto --scope user lsl. Done means Update handles newly required dependencies through a prompt or automatic installation.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.