Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

omnipkg v1.0.2 - Added Uninstall Feature #2

Discussion options

🧨 Release v1.0.2 — "Uninstalled with Prejudice"

✨ Highlights

  • Introducing omnipkg uninstall: A new, intelligent command that ensures complete and thorough removal of packages and their associated metadata. This isn’t just pip uninstall; this is surgical removal—dependencies, cached data, the entire footprint.
  • Redis-Powered Metadata Purge: omnipkg now leverages its Redis knowledge base to precisely identify and remove all traces of a package, including "bubble" versions and cached data. Zero-residue cleanup that no other Python tool even attempts.
  • Automatic Version Detection: No need to specify which version to remove. omnipkg uninstall automatically detects all installed versions of a package (both active and bubbled) and offers to clean them all.

💥 Real-World Example: Erasing uv

Let’s see this in action with uv. When we downgraded uv from 0.8.5 to 0.7.14, omnipkg cleverly created an isolated "bubble" to protect our main environment. Many package managers would leave behind an orphan environment or an incomplete mess, but omnipkg handles this gracefully.

First, let’s remove the primary installation:

$ omnipkg uninstall uv==0.8.5
Processing uninstall for: uv==0.8.5
Found 1 installation(s) to remove:
 - v0.8.5 (active)
🤔 Are you sure you want to proceed? (y/N): y
🗑️ Uninstalling 'uv' from main environment...
 Successfully uninstalled uv-0.8.5
✅ Uninstallation complete.

Now, the main environment is clean, but the isolated 0.7.14 bubble still exists. A quick omnipkg status shows us the clean separation:

$ omnipkg status
...
📦 Isolated Package Versions (85):
 - 📁 uv-0.7.14 (0.0 MB)
...

Notice the uv-0.7.14 bubble. Now, let’s see what a truly thorough uninstallation looks like. We target the bubble itself, and omnipkg knows exactly what to do:

$ omnipkg uninstall uv==0.7.14
Processing uninstall for: uv==0.7.14
Found 1 installation(s) to remove:
 - v0.7.14 (bubble)
🤔 Are you sure you want to proceed? (y/N): y
🗑️ Deleting bubble: uv-0.7.14
✅ Uninstallation complete.

Just like that, uv is completely gone—no files, no metadata, no residue. We don’t just uninstall a file. We delete the entire bubble, its metadata, and all of its dependencies, ensuring zero-residue cleanup.

🧠 Under the Hood

The new uninstall command is now fully integrated with our memory display, status reporting, and Redis knowledge base. This ensures that when you remove a package, you are truly removing it from the entire omnipkg ecosystem, whether it was in the main environment or an isolated bubble.

  • Fully integrated with Redis memory display
  • Synchronized with status, info, and activate commands
  • Bubble cleaner handles nested dependencies
  • Prevents orphan bubbles, ghost data, and partial states

This discussion was created from the release omnipkg v1.0.2 - Added Uninstall Feature.
You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /