omnipkg v1.0.2 - Added Uninstall Feature

🧨 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

omnipkg v1.0.1 - Pushing updated README to PyPi.

Pushing README changes to PyPi.

omnipkg v1.0.0: The End of Dependency Hell

omnipkg v1.0.0: The End of Dependency Hell

After extensive development and rigorous validation, omnipkg v1.0.0 is now publicly available.

This isn't just another package manager. It's a fundamental paradigm shift built on one revolutionary premise: you should never have to choose between package versions again.

The Persistent Problem We've Solved

Python developers have long struggled with dependency gridlock. Version conflicts force impossible choices: break your environment or abandon needed packages. Virtual environments create fragmentation and maintenance overhead.

omnipkg eliminates these compromises entirely.

How It Works: Bubble Isolation Technology

omnipkg introduces package bubbling - a breakthrough isolation system that allows conflicting versions to coexist seamlessly. When you install a conflicting package, omnipkg automatically:

1. Detects conflicts via real-time environment snapshots
2. Creates secure bubbles for problematic versions
3. Performs integrity checks using SHA-256 hashing
4. Deduplicates dependencies (60% average space savings)
5. Maintains full functionality of all versions

The result? 14+ GB of packages coexisting peacefully - including multiple PyTorch versions and ML stacks - where traditional tools fail.

Performance Benchmarks

• Knowledge base updates: 8 packages/second from scratch
• Delta caching: Near-instant subsequent operations
• Runtime switching: Faster than terminal streams
• Storage efficiency: 60% average savings via SHA-256 deduplication
• Full validation: Complete NumPy/SciPy install/run/swap in <30s
• Speed: Outperforms raw pip with full protection

Making the Impossible Achievable

🔬 Live Example: Safe Flask-Login Downgrade

# Install conflicting flask-login version
$ omnipkg install flask-login==0.4.1

📸 Taking LIVE pre-installation snapshot...
    - Found 545 packages

🛡️  DOWNGRADE PROTECTION ACTIVATED!
-> Detected conflict: flask-login v0.6.3 → v0.4.1
🫧 Creating bubble for flask-login v0.4.1
    -> Strategy 1: pip dry-run...
    -> Strategy 2: PyPI API...
    ✅ Dependencies resolved via PyPI API
📦 Installing to temporary location...
🧹 Creating deduplicated bubble...
⚡️ Loading hash index from cache...
📈 Loaded 203,032 file hashes
⚠️  Native isolation: MarkupSafe
✅ Bubble created: 151 files copied, 188 deduplicated
📊 Space saved: 55.5%
🔄 Restoring flask-login v0.6.3...

✅ Environment secured!

# Verify final state
$ omnipkg info flask-login

📋 flask-login STATUS:
----------------------------------------
🎯 Active: 0.6.3 (protected)
🫧 Available: 0.4.1
📊 Space Saved: 55.5% (188 files deduplicated)
🔄 Switch: omnipkg activate flask-login==0.4.1

You now have both versions available without virtual environments or conflicts.

Need stronger proof? Witness our ultimate validation.

🔥 Ultimate Validation: NumPy & SciPy Version Matrix

(omnipkg_heaven) $ omnipkg validate

============================================================
  🚀 omnipkg Ultimate Validation Suite
============================================================
⚠️ Downloads several hundred MB (takes 2-5 minutes)

Run validation? (y/n): y

============================================================
  🚀 PHASE 1: Clean Environment Preparation
============================================================
...
Successfully installed numpy-1.26.4

🔬 Analyzing changes...

🛡️  PROTECTION ACTIVATED!
    -> Handling: numpy v2.3.2 → v1.26.4
🫧 Creating bubble for numpy v1.26.4
    ...
    ✅ Bubble created: 1407 files
    📊 Space saved: 0.0%
    🔄 Restoring numpy v2.3.2...

✅ Environment secured!

============================================================
  🚀 PHASE 2: Multi-Version Bubble Creation
============================================================
...
--- Creating numpy==1.24.3 bubble ---
🫧 Isolating numpy v1.24.3
    ✅ Bubble created: 1363 files

--- Creating scipy==1.12.0 bubble ---
🫧 Isolating scipy v1.12.0
    ✅ Bubble created: 3551 files

============================================================
  🚀 PHASE 3: Runtime Validation
============================================================

💥 NUMPY VERSION SWITCHING:

⚡ Activating numpy==1.24.3
 ✅ Version: 1.24.3
 🔢 Array sum: 6

⚡ Activating numpy==1.26.4
 ✅ Version: 1.26.4
 🔢 Array sum: 6

🔥 SCIPY EXTENSION VALIDATION:

🌋 Activating scipy==1.12.0
 ✅ Version: 1.12.0
 ♻️ Sparse matrix: 3 non-zeros

🌋 Activating scipy==1.16.1
 ✅ Version: 1.16.1
 ♻️ Sparse matrix: 3 non-zeros

🤯 COMBINATION TESTING:

🌀 Mix: numpy==1.24.3 + scipy==1.12.0
...
   🧪 Compatibility: [1. 2. 3.]

🌀 Mix: numpy==1.26.4 + scipy==1.16.1
...
   🧪 Compatibility: [1. 2. 3.]


 🚀 VALIDATION SUCCESSFUL! 🎇

============================================================
  🚀 PHASE 4: Environment Restoration
============================================================
   - Removing bubble: numpy-1.24.3
   - Removing bubble: numpy-1.26.4
   - Removing bubble: scipy-1.12.0

✅ Environment restored to initial state.

v1.0.0 Core Features

🛡️ Conflict Protection Engine
Real-time conflict detection and bubble initiation

🫧 Secure Bubble System
SHA-256 verified isolation with cross-bubble deduplication

🧠 Redis Knowledge Base
Cached metadata and dependency resolution

🔐 Integrity Verification
Security scanning and hash-based validation

🔀 Runtime Loader (Experimental)
Version switching in active scripts

🚀 Built-in Demonstrations
Try omnipkg demo and omnipkg validate

📊 Environment Analytics
Version tracking and health monitoring

Installation

pip install omnipkg
omnipkg demo  # See the system in action
omnipkg stress-test # See numpy/scipy version switching at runtime.

Licensing

Community Edition: GNU AGPLv3
Commercial License: Enterprise integration and proprietary use

Enterprise Features:

• Priority support and consulting
• Custom bubble strategies
• Compliance reporting
• On-premises deployment
• Team licensing

Contact: [email protected]

---

The era of dependency compromises is over.
Stop wrestling environments. Start building solutions.

---

Ready to experience frictionless packaging?

pip install omnipkg
omnipkg demo  # See multiple ecosystems coexist