maliput / maliput_infrastructure

Driving simulation repository for workspace .repo indexes, Makefiles, etc.

BSD 3-Clause "New" or "Revised" License

0 stars 2 forks source link

Open sourcing drake_vendor #173

Open agalbachicar opened 3 years ago

agalbachicar commented 3 years ago

drake_vendor will be open sourced and with it a few things should change to make it compatible with our workspace:

[ ] URLs in repos files should be fixed to use the correct and final organization.
[ ] CI should be aware of this change and drake_vendor should be installed into the workspace as the other open source repositories.
[x] We should create and document new workflow to try newer drake installations.

agalbachicar commented 3 years ago

FYI @stonier

stonier commented 3 years ago

We should create and document new workflow to try newer drake installations.

Do you currently have any documentation for this w.r.t. upgrading against the maliput - delphyne repos? The drake_vendor README has documentation for how to try a newer version in a workspace, but not specific to maliput-delphyne. I imagine that'd be useful for us.

agalbachicar commented 3 years ago

The drake_vendor README has documentation for how to try a newer version in a workspace, but not specific to maliput-delphyne

Do you mean something similar to the following?

Generate a new branch on all the drake_vendor dependent repositories with the same branch name for all.
Change the package.xml of those packages where drake_vendor is located to add the attribute version_eq=NEW_DRAKE_VERSION"
Build and test

agalbachicar commented 3 years ago

175 to document the above procedure.

agalbachicar commented 3 years ago

I think this is a no-op now that we have maliput_drake (see #232). @stonier any thoughts?

francocipollone commented 3 years ago

I think this is a no-op now that we have maliput_drake (see #232). @stonier any thoughts?

I guess it will depend entirely on whether delphyne is being opensourced or not.