-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference repos files in a repos file #241
Comments
I worked on this exact feature and have a working prototype, see here: #148 Unfortunately, it didn't go anywhere as far as merging it into this repo. |
Thanks, I'll take a look |
It might be possible to extract this feature into a separate tool that takes the "extension" repos file as an input and outputs the combined repos file. Then you could just pipe the output into |
@christophebedard was there anything left to do in #148 ? Or is it a matter of getting more feedback from @dirk-thomas ? Looks to me that your PR already achieves the goal you wanted, right? |
@esteve yes the PR is pretty complete. I think the repo is in light maintenance mode, since Dirk has stopped needing this tool. Maybe @dirk-thomas would be open to letting other people take over maintainership? |
@christophebedard thanks for the info. Given that |
@esteve should probably bring this up in a https://github.com/ros2/ros2 issue. I think Dirk is enjoying life these days 😄 |
@christophebedard I've created #242, but if we don't get a response, I'll move the discussion to Discourse |
Was there ever any progress on this issue? I've got a very similar use case to the one above. |
No progress unfortunately. |
@christophebedard I opened #242 a long time ago, but didn't get a response from @dirk-thomas . Given that you showed interest in helping maintain |
Consider the following situation:
It would be nice to only define the core config once and include or inline it somehow in each project specific definition instead of repeating the same 50 lines 5 times.
Has this been considered before?
The text was updated successfully, but these errors were encountered: