Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Install To Platform-Standard Locations | Reduce Home Directory Clutter

Open
#476 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #489 by @taep96 — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli, tooling

Research direction

Start by locating where espup currently places files directly in $HOME and how export-esp.sh is handled. Review the directories crate's platform-location behavior and the proposed fallback order. Done means installation uses the standard location, with the requested optional symlink and extensionless script behavior addressed.

Written by the indexing model from the issue text.

Description

enhancement feature request

Motivations

Files are currently placed directly in $HOME, which creates clutter. Using standard platform directories would improve system integration.

  • Would you like to implement this feature? — Not sure.

Solution

  1. Use directories crate with the following fallback order:

    1. $XDG_DATA_HOME/espup
    2. $HOME/.local/share/espup
    3. $HOME/.espup
  2. Add flag to optionally symlink export-esp.sh from $HOME to $XDG_DATA_HOME/espup/export-esp.sh

  3. Create an extension-less version of the script with a shebang and export to $PATH - the $HOME symlink could point to this instead

Alternatives

  • Add an environment variable to customize the location — $ESP_HOME

Additional context

The directories crate provides cross-platform support for standard directory locations.

Dominant language
Rust
Stars
460
Forks
37
Avg merge
2d 16h
Merged PRs (30d)
6

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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.

More from esp-rs/espup

All issues in esp-rs/espup

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.