You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are hosting a private debian repository to store internal software and libraries as deb packages.
Is it possible to add such a debian repository by adding a x.list file to the apt sources.list.d?
Additionally, we use a private server, hosting a rosdep.yaml which makes the matching from ROS package dependencies to the debian packages. Is it possible to add such thing as well?
I tried the custom.sh script to add these, but it is running after rosdep has tried to find the dependencies.
The text was updated successfully, but these errors were encountered:
I guess you are right, currently this is not possible via custom.sh and it's not supported as a native feature.
However, it might be quite easy to implement. The dependencies are currently found via rosdep in this line, so you would need to set up everything before that line. A good place might be below this block, since that's where the ROS apt repositories are added.
My suggestion would be to add a custom .list file, if it exists. The file handling logic and how it's brought into the image could be implemented similar to how custom.sh is treated here.
I would be more than happy to review a pull request, if you were to implement this feature yourself. Note that it might make sense to build images locally for testing purposes.
We are hosting a private debian repository to store internal software and libraries as deb packages.
Is it possible to add such a debian repository by adding a x.list file to the apt sources.list.d?
Additionally, we use a private server, hosting a rosdep.yaml which makes the matching from ROS package dependencies to the debian packages. Is it possible to add such thing as well?
I tried the custom.sh script to add these, but it is running after rosdep has tried to find the dependencies.
The text was updated successfully, but these errors were encountered: