Add Flox package build configuration for publishing

[billlevine]

Summary

This PR reorganizes the project structure and adds build configuration to enable publishing spdx-to-mermaid as a standalone Flox package that can be installed in any environment.

Changes

Project Reorganization

• Moved Python source to package/ subdirectory - This isolates the Python package from the .flox/ environment directory, preventing symlink issues during package builds
• Preserved git history - Used git mv to maintain full file history during reorganization

Build Configuration

• Added [build.spdx-to-mermaid] section to .flox/env/manifest.toml:
  • Builds Python wheel using uv build
  • Bundles all dependencies (spdx-tools, rdflib, etc.)
  • Creates wrapper script with proper PYTHONPATH
  • Only requires python3 as runtime dependency
• Updated .gitignore to exclude build artifacts while preserving .flox/ directory
• Updated Justfile to reference the new package/ directory

Package Details

• Package name: spdx-to-mermaid
• Version: 0.1.0
• Runtime dependency: python3 only (all Python deps bundled)
• Entry point: /bin/spdx-to-mermaid CLI tool

Testing

Build tested successfully:

flox build spdx-to-mermaid
./result-spdx-to-mermaid/bin/spdx-to-mermaid --help

Publishing

After merge, the package can be published with:

flox publish spdx-to-mermaid

Users will then be able to install it:

flox install spdx-to-mermaid
spdx-to-mermaid myfile.spdx.json

Notes

The visualization features (HTTP server, mermaid-cli, chromium) remain in the development environment. The published package is the core CLI tool only, which keeps it lightweight and widely usable.

[billlevine]

Update: Added Viewer Environment

Added a standalone environment that can be shared via FloxHub:

What's New

Standalone Viewer Environment in :

• Separate Flox environment for visualization only
• Installs published spdx-to-mermaid package from FloxHub catalog
• Includes all visualization tools: mermaid-cli, chromium, HTTP server, just
• Complete with viewer.html, configs, and Justfile with convenience commands
• Lightweight - no build tools or Python source code

Two Environments

The repository now has two distinct environments:

1. Development Environment (root): For building and publishing the package
2. Viewer Environment (spdx-viewer/): For consuming and visualizing SPDX files

Usage After Publishing

Once the package is published:

1. Uncomment spdx-to-mermaid in spdx-viewer/.flox/env/manifest.toml
2. Push to FloxHub: flox push
3. Share with team: flox pull owner/spdx-viewer

This makes it easy for teams to use the visualization tools without needing the full development environment.

[billlevine]

Update: Simplified Viewer Environment

The viewer environment has been simplified based on feedback:

Changes

Removed dependencies:

• Removed just - no longer needed

Added bash functions in profile:
All visualization commands are now bash functions defined in the [profile.common] section of manifest.toml:

# After flox activate, these functions are available:
spdx-show <file> [options]    # View SPDX as interactive diagram
spdx-svg <file> [out] [opts]  # Convert to SVG file
spdx-serve                     # Start HTTP server
spdx-stop                      # Stop services

Published package installed:

• Now installs flox/spdx-to-mermaid from the catalog
• Restricted to x86_64-linux (where it was published)

Benefits

1. Fewer dependencies - One less package to install
2. Self-contained - Everything in manifest.toml
3. Better UX - Shows welcome message with available commands on activation
4. More portable - Works in bash/zsh without external tools

Usage

cd spdx-viewer
flox activate

# Functions are now available
spdx-show myfile.spdx.json --compact
spdx-svg myfile.spdx.json output.svg

The functions work in interactive shell mode. The environment is now ready to push to FloxHub.