pixi-ros 0.2.0__tar.gz → 0.4.0__tar.gz

{pixi_ros-0.2.0 → pixi_ros-0.4.0}/.github/workflows/ci.yml

@@ -15,7 +15,7 @@ jobs:
       - uses: prefix-dev/setup-pixi@82d477f15f3a381dbcc8adc1206ce643fe110fb7 # v0.9.3
 
       - name: Format 
-        run: pixi run format --check
+        run: pixi run fmt --check
       - name: Lint
         run: pixi run lint
       - name: Test

{pixi_ros-0.2.0 → pixi_ros-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pixi-ros
-Version: 0.2.0
+Version: 0.4.0
 Summary: Pixi extension for ROS package management
 Project-URL: Homepage, https://github.com/ruben-arts/pixi-ros
 Project-URL: Repository, https://github.com/ruben-arts/pixi-ros
@@ -13,6 +13,7 @@ Requires-Dist: pathspec>=0.11.0
 Requires-Dist: py-rattler>=0.6.0
 Requires-Dist: pyyaml>=6.0
 Requires-Dist: rich>=13.0.0
+Requires-Dist: rosdistro>=0.9.0
 Requires-Dist: tomlkit>=0.12.0
 Requires-Dist: typer>=0.12.0
 Description-Content-Type: text/markdown
@@ -63,10 +64,16 @@ pixi-ros init --distro humble
 This will:
 1. Discover all ROS packages in your workspace (by finding `package.xml` files)
 2. Read dependencies from each `package.xml`
-3. Map ROS package names to conda packages
+3. **Validate and resolve** each dependency using the priority system:
+   - Skip workspace packages (built locally)
+   - Use custom mappings from YAML files
+   - Query ROS distro index for ROS packages
+   - Auto-detect packages on conda-forge
+   - Flag packages that can't be found
 4. Generate/update `pixi.toml` with proper channels and dependencies
-5. Check package availability and warn about missing packages
+5. Check package availability in conda channels for each platform
 6. Create helpful build/test/clean tasks
+7. Display detailed validation results with source information
 
 ### Install and Build
 
@@ -88,26 +95,66 @@ pixi shell
 
 ## How It Works
 
-### Dependency Mapping
+### Dependency Mapping & Validation
 
-`pixi-ros` reads all dependency types from `package.xml` files.
-It then does a best effort mapping of ROS package names to conda packages.
+`pixi-ros` reads all dependency types from `package.xml` files and intelligently resolves them to conda packages using a **priority-based validation system**.
 
-- **ROS packages**: `ros-{distro}-{package}` from robostack channels (e.g., `ros-humble-rclcpp`)
-- **System packages**: Mapped to conda-forge equivalents (e.g., `cmake`, `eigen`)
-- **Platform-specific packages**: Different mappings per platform (e.g., OpenGL → `libgl-devel` on Linux, X11 packages on macOS)
+#### Validation Priority Order
+
+When resolving a ROS package dependency, `pixi-ros` checks sources in this order:
+
+1. **Workspace packages** (local source) → Skipped, won't be added to dependencies
+2. **Mapping files** → Use custom conda package mappings from the embedded mapping.
+3. **ROS distribution** → Query the official ROS distro index for `ros-{distro}-{package}` packages
+4. **conda-forge** (auto-detection) → Search conda-forge for packages without ros-distro prefix
+5. **NOT FOUND** → Mark as unavailable and comment out in `pixi.toml`
+
+#### Package Sources
+
+The dependency tables show where each package comes from:
+
+- **ROS {distro}**: Official ROS distribution packages from robostack (e.g., `ros-humble-rclcpp`)
+- **Mapping**: Custom mappings from YAML files (e.g., `cmake` → `cmake`, `udev` → `libusb + libudev`)
+- **conda-forge**: Auto-detected packages available directly on conda-forge
+- **Workspace**: Local packages in your workspace (skipped from dependencies)
+- **NOT FOUND**: Packages that couldn't be resolved (commented out in `pixi.toml`)
 
 The mapping rules are defined in YAML files (see `src/pixi_ros/data/conda-forge.yaml`) and can be customized by placing your own mapping files in `pixi-ros/*.yaml` or `~/.pixi-ros/*.yaml`.
 
-After the mapping, it validates package availability in the configured channels for each target platform. This starts a connection with `https://prefix.dev` to check if packages exist.
+After dependency resolution, `pixi-ros` validates package availability in the configured channels for each target platform by connecting to `https://prefix.dev`.
+
+### Example Output
 
-### Example
+When you run `pixi-ros init --distro humble`, you'll see validation results:
+
+```
+Found 2 package(s): my_package, other_package
+Initializing ROS humble distribution validator...
+
+╭─────────────────── Package: my_package ───────────────────╮
+│ ROS Dependency │ Type    │ Conda Packages          │ Source       │
+├────────────────┼─────────┼─────────────────────────┼──────────────┤
+│ rclcpp         │ Build   │ ros-humble-rclcpp       │ ROS humble   │
+│ std_msgs       │ Runtime │ ros-humble-std-msgs     │ ROS humble   │
+│ cmake          │ Build   │ cmake                   │ Mapping      │
+│ eigen          │ Build   │ eigen                   │ conda-forge  │
+╰────────────────┴─────────┴─────────────────────────┴──────────────╯
+
+Validation Summary:
+  ✓ 2 workspace packages (skipped)
+  ✓ 1 packages from mappings
+  ✓ 5 packages from ROS humble distro
+  ✓ 1 packages from conda-forge (auto-detected)
+
+  Total external dependencies: 7
+```
 
 Given a `package.xml` with:
 
 ```xml
 <depend>rclcpp</depend>
 <build_depend>ament_cmake</build_depend>
+<build_depend>cmake</build_depend>
 <exec_depend>std_msgs</exec_depend>
 ```
 
@@ -115,17 +162,57 @@ Given a `package.xml` with:
 
 ```toml
 [dependencies]
-ros-humble-ament-cmake = "*"
-ros-humble-rclcpp = "*"
-ros-humble-std-msgs = "*"
+# Base ROS dependencies
+ros-humble-ros-base = "*"
+pkg-config = "*"
+compilers = "*"
+make = "*"
+ninja = "*"
+
+# Build tools
+colcon-common-extensions = "*"
+
+# Workspace dependencies
+cmake = "*"                      # From mapping
+ros-humble-ament-cmake = "*"    # From ROS humble
+ros-humble-rclcpp = "*"         # From ROS humble
+ros-humble-std-msgs = "*"       # From ROS humble
 ```
 
-## Supported ROS Distributions
+### Version Constraints
+
+`pixi-ros` supports version constraints from `package.xml` files and automatically applies them to the generated `pixi.toml`.
+
+#### Supported Version Attributes
 
-- ROS 2 Humble: https://prefix.dev/robostack-humble
-- ROS 2 Iron: https://prefix.dev/robostack-iron
-- ROS 2 Jazzy: https://prefix.dev/robostack-jazzy
-- ROS 2 Rolling: https://prefix.dev/robostack-rolling
+You can specify version requirements in your `package.xml` using standard ROS version attributes:
+
+| package.xml attribute | pixi.toml constraint | Description |
+|----------------------|----------------------|-------------|
+| `version_eq="X.Y.Z"` | `==X.Y.Z` | Exactly version X.Y.Z |
+| `version_gte="X.Y.Z"` | `>=X.Y.Z` | Version X.Y.Z or newer |
+| `version_gt="X.Y.Z"` | `>X.Y.Z` | Newer than version X.Y.Z |
+| `version_lte="X.Y.Z"` | `<=X.Y.Z` | Version X.Y.Z or older |
+| `version_lt="X.Y.Z"` | `<X.Y.Z` | Older than version X.Y.Z |
+
+Multiple constraints can be combined on the same dependency and will be joined with commas in the output.
+
+Given a `package.xml` with version constraints:
+
+```xml
+<depend version_gte="3.12.4">cmake</depend>
+<build_depend version_gte="3.3.0" version_lt="4.0.0">eigen</build_depend>
+<exec_depend version_eq="1.2.3">boost</exec_depend>
+```
+
+`pixi-ros init` generates:
+
+```toml
+[dependencies]
+cmake = ">=3.12.4"
+eigen = ">=3.3.0,<4.0.0"
+boost = "==1.2.3"
+```
 
 ## Command Reference
 
@@ -147,13 +234,16 @@ pixi-ros init
 
 **What it does:**
 - Scans workspace for `package.xml` files
-- Reads all dependency types (build, exec, test)
+- Reads all dependency types (build, exec, test) and version constraints
+- **Validates dependencies** using the priority-based system (workspace → mapping → ROS distro → conda-forge)
 - Maps ROS dependencies to conda packages for each platform
+- Applies version constraints from package.xml to pixi.toml dependencies
 - Configures robostack channels
 - Checks package availability per platform
 - Creates build tasks using colcon
 - Generates helpful `README_PIXI.md`
 - Sets up platform-specific dependencies in `pixi.toml`
+- **Displays validation results** showing where each dependency was found
 
 **Running multiple times:**
 The command is idempotent - you can run it multiple times to update dependencies as your workspace changes.
@@ -261,12 +351,15 @@ workspace/
 
 ### Package Not Found
 
-If pixi-ros marks packages as "NOT FOUND":
+If pixi-ros marks packages as "NOT FOUND" (shown in red in the validation output):
+
+1. **Check the ROS distro**: Verify the package exists in robostack: https://prefix.dev/channels/robostack-{distro}
+2. **Check for typos**: Review your `package.xml` for spelling errors
+3. **Check conda-forge**: Some packages may be available directly on conda-forge without the `ros-distro-` prefix
+4. **Create a mapping**: Add a custom mapping in `pixi-ros/*.yaml` if the package has a different conda name
+5. **Add to workspace**: Consider including the package source in your workspace instead of depending on it
 
-1. Check if the package exists in robostack: https://prefix.dev/channels/robostack-{distro}
-2. Check for typos in `package.xml`
-3. Some packages may have different names - check mapping files
-4. Consider adding the package to your workspace instead of depending on it
+The validation table shows exactly where each dependency was checked, making it easier to diagnose issues.
 
 ### Different Package Names
 

{pixi_ros-0.2.0 → pixi_ros-0.4.0}/README.md

@@ -44,10 +44,16 @@ pixi-ros init --distro humble
 This will:
 1. Discover all ROS packages in your workspace (by finding `package.xml` files)
 2. Read dependencies from each `package.xml`
-3. Map ROS package names to conda packages
+3. **Validate and resolve** each dependency using the priority system:
+   - Skip workspace packages (built locally)
+   - Use custom mappings from YAML files
+   - Query ROS distro index for ROS packages
+   - Auto-detect packages on conda-forge
+   - Flag packages that can't be found
 4. Generate/update `pixi.toml` with proper channels and dependencies
-5. Check package availability and warn about missing packages
+5. Check package availability in conda channels for each platform
 6. Create helpful build/test/clean tasks
+7. Display detailed validation results with source information
 
 ### Install and Build
 
@@ -69,26 +75,66 @@ pixi shell
 
 ## How It Works
 
-### Dependency Mapping
+### Dependency Mapping & Validation
 
-`pixi-ros` reads all dependency types from `package.xml` files.
-It then does a best effort mapping of ROS package names to conda packages.
+`pixi-ros` reads all dependency types from `package.xml` files and intelligently resolves them to conda packages using a **priority-based validation system**.
 
-- **ROS packages**: `ros-{distro}-{package}` from robostack channels (e.g., `ros-humble-rclcpp`)
-- **System packages**: Mapped to conda-forge equivalents (e.g., `cmake`, `eigen`)
-- **Platform-specific packages**: Different mappings per platform (e.g., OpenGL → `libgl-devel` on Linux, X11 packages on macOS)
+#### Validation Priority Order
+
+When resolving a ROS package dependency, `pixi-ros` checks sources in this order:
+
+1. **Workspace packages** (local source) → Skipped, won't be added to dependencies
+2. **Mapping files** → Use custom conda package mappings from the embedded mapping.
+3. **ROS distribution** → Query the official ROS distro index for `ros-{distro}-{package}` packages
+4. **conda-forge** (auto-detection) → Search conda-forge for packages without ros-distro prefix
+5. **NOT FOUND** → Mark as unavailable and comment out in `pixi.toml`
+
+#### Package Sources
+
+The dependency tables show where each package comes from:
+
+- **ROS {distro}**: Official ROS distribution packages from robostack (e.g., `ros-humble-rclcpp`)
+- **Mapping**: Custom mappings from YAML files (e.g., `cmake` → `cmake`, `udev` → `libusb + libudev`)
+- **conda-forge**: Auto-detected packages available directly on conda-forge
+- **Workspace**: Local packages in your workspace (skipped from dependencies)
+- **NOT FOUND**: Packages that couldn't be resolved (commented out in `pixi.toml`)
 
 The mapping rules are defined in YAML files (see `src/pixi_ros/data/conda-forge.yaml`) and can be customized by placing your own mapping files in `pixi-ros/*.yaml` or `~/.pixi-ros/*.yaml`.
 
-After the mapping, it validates package availability in the configured channels for each target platform. This starts a connection with `https://prefix.dev` to check if packages exist.
+After dependency resolution, `pixi-ros` validates package availability in the configured channels for each target platform by connecting to `https://prefix.dev`.
+
+### Example Output
 
-### Example
+When you run `pixi-ros init --distro humble`, you'll see validation results:
+
+```
+Found 2 package(s): my_package, other_package
+Initializing ROS humble distribution validator...
+
+╭─────────────────── Package: my_package ───────────────────╮
+│ ROS Dependency │ Type    │ Conda Packages          │ Source       │
+├────────────────┼─────────┼─────────────────────────┼──────────────┤
+│ rclcpp         │ Build   │ ros-humble-rclcpp       │ ROS humble   │
+│ std_msgs       │ Runtime │ ros-humble-std-msgs     │ ROS humble   │
+│ cmake          │ Build   │ cmake                   │ Mapping      │
+│ eigen          │ Build   │ eigen                   │ conda-forge  │
+╰────────────────┴─────────┴─────────────────────────┴──────────────╯
+
+Validation Summary:
+  ✓ 2 workspace packages (skipped)
+  ✓ 1 packages from mappings
+  ✓ 5 packages from ROS humble distro
+  ✓ 1 packages from conda-forge (auto-detected)
+
+  Total external dependencies: 7
+```
 
 Given a `package.xml` with:
 
 ```xml
 <depend>rclcpp</depend>
 <build_depend>ament_cmake</build_depend>
+<build_depend>cmake</build_depend>
 <exec_depend>std_msgs</exec_depend>
 ```
 
@@ -96,17 +142,57 @@ Given a `package.xml` with:
 
 ```toml
 [dependencies]
-ros-humble-ament-cmake = "*"
-ros-humble-rclcpp = "*"
-ros-humble-std-msgs = "*"
+# Base ROS dependencies
+ros-humble-ros-base = "*"
+pkg-config = "*"
+compilers = "*"
+make = "*"
+ninja = "*"
+
+# Build tools
+colcon-common-extensions = "*"
+
+# Workspace dependencies
+cmake = "*"                      # From mapping
+ros-humble-ament-cmake = "*"    # From ROS humble
+ros-humble-rclcpp = "*"         # From ROS humble
+ros-humble-std-msgs = "*"       # From ROS humble
 ```
 
-## Supported ROS Distributions
+### Version Constraints
+
+`pixi-ros` supports version constraints from `package.xml` files and automatically applies them to the generated `pixi.toml`.
+
+#### Supported Version Attributes
 
-- ROS 2 Humble: https://prefix.dev/robostack-humble
-- ROS 2 Iron: https://prefix.dev/robostack-iron
-- ROS 2 Jazzy: https://prefix.dev/robostack-jazzy
-- ROS 2 Rolling: https://prefix.dev/robostack-rolling
+You can specify version requirements in your `package.xml` using standard ROS version attributes:
+
+| package.xml attribute | pixi.toml constraint | Description |
+|----------------------|----------------------|-------------|
+| `version_eq="X.Y.Z"` | `==X.Y.Z` | Exactly version X.Y.Z |
+| `version_gte="X.Y.Z"` | `>=X.Y.Z` | Version X.Y.Z or newer |
+| `version_gt="X.Y.Z"` | `>X.Y.Z` | Newer than version X.Y.Z |
+| `version_lte="X.Y.Z"` | `<=X.Y.Z` | Version X.Y.Z or older |
+| `version_lt="X.Y.Z"` | `<X.Y.Z` | Older than version X.Y.Z |
+
+Multiple constraints can be combined on the same dependency and will be joined with commas in the output.
+
+Given a `package.xml` with version constraints:
+
+```xml
+<depend version_gte="3.12.4">cmake</depend>
+<build_depend version_gte="3.3.0" version_lt="4.0.0">eigen</build_depend>
+<exec_depend version_eq="1.2.3">boost</exec_depend>
+```
+
+`pixi-ros init` generates:
+
+```toml
+[dependencies]
+cmake = ">=3.12.4"
+eigen = ">=3.3.0,<4.0.0"
+boost = "==1.2.3"
+```
 
 ## Command Reference
 
@@ -128,13 +214,16 @@ pixi-ros init
 
 **What it does:**
 - Scans workspace for `package.xml` files
-- Reads all dependency types (build, exec, test)
+- Reads all dependency types (build, exec, test) and version constraints
+- **Validates dependencies** using the priority-based system (workspace → mapping → ROS distro → conda-forge)
 - Maps ROS dependencies to conda packages for each platform
+- Applies version constraints from package.xml to pixi.toml dependencies
 - Configures robostack channels
 - Checks package availability per platform
 - Creates build tasks using colcon
 - Generates helpful `README_PIXI.md`
 - Sets up platform-specific dependencies in `pixi.toml`
+- **Displays validation results** showing where each dependency was found
 
 **Running multiple times:**
 The command is idempotent - you can run it multiple times to update dependencies as your workspace changes.
@@ -242,12 +331,15 @@ workspace/
 
 ### Package Not Found
 
-If pixi-ros marks packages as "NOT FOUND":
+If pixi-ros marks packages as "NOT FOUND" (shown in red in the validation output):
+
+1. **Check the ROS distro**: Verify the package exists in robostack: https://prefix.dev/channels/robostack-{distro}
+2. **Check for typos**: Review your `package.xml` for spelling errors
+3. **Check conda-forge**: Some packages may be available directly on conda-forge without the `ros-distro-` prefix
+4. **Create a mapping**: Add a custom mapping in `pixi-ros/*.yaml` if the package has a different conda name
+5. **Add to workspace**: Consider including the package source in your workspace instead of depending on it
 
-1. Check if the package exists in robostack: https://prefix.dev/channels/robostack-{distro}
-2. Check for typos in `package.xml`
-3. Some packages may have different names - check mapping files
-4. Consider adding the package to your workspace instead of depending on it
+The validation table shows exactly where each dependency was checked, making it easier to diagnose issues.
 
 ### Different Package Names