Silvio Traversaro

> See also #151 for a related old discussion on this. Actually that discussion refer to https://github.com/rapyuta-robotics/depthai_ros/, while this to discussion to https://github.com/luxonis/depthai-ros, not sure how the two are related.

Cool, thanks! Just some pointer I found: * `depthai-ros` depends on `depthai-core`, that is also packaged in the ROS build farm (see https://github.com/ros/rosdistro/pull/40111) * `depthai-core` has a branch for ros...

> Looks like Tobias may have beaten us to it a few weeks ago though! https://github.com/RoboStack/ros-noetic/actions/runs/8902332643 Good point, let's cross link to avoid forgetting about it: https://github.com/RoboStack/ros-noetic/pull/470 .

Also https://github.com/RoboStack/ros-noetic/pull/441#issuecomment-1913420942 is related.

Hello @sujitmandal, please change the PR and the description of the PR to mention which package you are adding. Once that is done, please follow https://github.com/conda-forge/staged-recipes?tab=readme-ov-file#12-my-pull-request-passes-all-checks-but-hasnt-received-any-attention-how-do-i-call-attention-to-my-pr--what-is-the-customary-amount-of-time-to-wait to ask for a...

Please check the first point of the checklist, i.e. " Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml"." At the moment the title is a generic...

It seems that this recipe is a `noarch: python`, you can check the instructions in https://conda-forge.org/docs/maintainer/knowledge_base.html#noarch-python . More in general, I am not a reviewer here, so you may want...

Sorry for resurrecting this old discussion, but it seems this is the only discussion about the use of `cpu` and `cuda` build strings that more and less are now used...

We discussed about this in the ros-general Discord channel, see https://discord.com/channels/1077825543698927656/1077836632658542634/1359493668012163082 . My analysis on possible (alternative) solutions were: * Add a post-install script to the windows binary archive that...

> Please consider standardizing on PowerShell for Windows installation scripts. I see a chance here to automate more steps of the setup process but would be too complex to do...