Great question—this is exactly the kind of thing that trips up folks moving from quick scripts to proper Unix-style tools. Let's break this down step by step:

1. Where to Place Your Application Directory #

Unix systems follow the Filesystem Hierarchy Standard (FHS) for consistent file organization. Here are the standard, clean options:

• System-wide (all users can access):
  • /usr/local/lib/your-tool-name: Best for tools that integrate with system-level resources (this directory is reserved for locally installed software, so it won't be overwritten by system package managers like apt or yum).
  • /opt/your-tool-name: Ideal for self-contained applications that don't rely on system libraries—this keeps all your tool's files bundled in one isolated location.
• User-specific (only your account can access):
  • ~/.local/lib/your-tool-name: A hidden, user-specific counterpart to /usr/local/lib—no sudo permissions required.
  • ~/opt/your-tool-name: A user-level version of /opt for standalone tools.

Avoid dumping files directly into /usr/bin—you're right that this creates cleanup headaches and violates FHS conventions.

2. Adding the Main Script to PATH for Global Execution #

The cleanest way to make your tool callable from any directory is to create a symbolic link from your main script to a directory that's already in your system's PATH. Here's how:

First, prep your main script #

Make sure your script has a shebang at the top to specify the Python interpreter:

#!/usr/bin/env python3

Then set it as executable:

chmod +x your-main-script.py

Option 1: System-wide access (requires sudo) #

Most systems have /usr/local/bin in the default PATH—create a symlink here pointing to your script:

sudo ln -s /usr/local/lib/your-tool-name/your-main-script.py /usr/local/bin/your-tool-command

Now you can run your-tool-command from any directory.

Option 2: User-specific access (no sudo) #

Use ~/.local/bin (create it if it doesn't exist):

mkdir -p ~/.local/bin
ln -s ~/.local/lib/your-tool-name/your-main-script.py ~/.local/bin/your-tool-command

If ~/.local/bin isn't in your PATH, add this line to your ~/.bashrc, ~/.zshrc, or equivalent shell config file:

export PATH="$HOME/.local/bin:$PATH"

Then reload the config with source ~/.bashrc (or your shell's equivalent).

3. Creating an Install/Uninstall Script for Easy Deployment #

You can write simple bash scripts to automate deployment and cleanup. Here are working examples:

Install Script (system-wide) #

Save as install.sh, make it executable (chmod +x install.sh), and run with sudo ./install.sh:

#!/bin/bash

TOOL_NAME="your-tool"
TOOL_DIR="/usr/local/lib/$TOOL_NAME"
BIN_LINK="/usr/local/bin/$TOOL_NAME"

# Check for sudo privileges
if [ "$(id -u)" -ne 0 ]; then
    echo "Please run this script with sudo for system-wide installation."
    exit 1
fi

# Create tool directory if it doesn't exist
mkdir -p "$TOOL_DIR"

# Copy all tool files to the installation directory
cp -r ./* "$TOOL_DIR/"

# Make main script executable
chmod +x "$TOOL_DIR/your-main-script.py"

# Create/update symbolic link
ln -sf "$TOOL_DIR/your-main-script.py" "$BIN_LINK"

echo "✅ $TOOL_NAME installed successfully! Run '$TOOL_NAME' from any directory."

Uninstall Script (system-wide) #

Save as uninstall.sh, run with sudo ./uninstall.sh:

#!/bin/bash

TOOL_NAME="your-tool"
TOOL_DIR="/usr/local/lib/$TOOL_NAME"
BIN_LINK="/usr/local/bin/$TOOL_NAME"

if [ "$(id -u)" -ne 0 ]; then
    echo "Please run this script with sudo for system-wide uninstallation."
    exit 1
fi

# Remove symbolic link if it exists
if [ -L "$BIN_LINK" ]; then
    rm "$BIN_LINK"
    echo "🗑️ Removed symlink: $BIN_LINK"
fi

# Remove tool directory if it exists
if [ -d "$TOOL_DIR" ]; then
    rm -rf "$TOOL_DIR"
    echo "🗑️ Removed tool directory: $TOOL_DIR"
fi

echo "✅ $TOOL_NAME uninstalled successfully."

For User-Specific Deployment #

Just modify the paths in the scripts to use ~/.local instead of /usr/local, and remove the sudo checks. For example:

TOOL_DIR="$HOME/.local/lib/$TOOL_NAME"
BIN_LINK="$HOME/.local/bin/$TOOL_NAME"

Extra Tips #

• If your tool uses configuration files, system-wide configs go in /etc/$TOOL_NAME/, user-specific configs in ~/.config/$TOOL_NAME/—add logic to your install script to copy these to the right places.
• Test your install/uninstall scripts in a safe environment first to avoid accidental file deletion.
• If your tool depends on specific Python packages, consider including a requirements.txt and adding a line to the install script to run pip install -r "$TOOL_DIR/requirements.txt".

内容的提问来源于stack exchange，提问作者Anselme Clergeot