Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] switch from com.spotify.docker.client to org.mandas.docker.client
On Thu, Jan 16, 2020 at 11:41 PM Homer, Tony <tony.homer@xxxxxxxxx> wrote:

I discussed this change with Roland at EclipseCon last year but haven’t had time to move forward until now.

 

In a nutshell, Spotify Docker Client is no longer being maintained [1].

As discussed in this issue [2], the damandalidis/dmandas fork [3] is bring actively maintained with an eye to staying ahead of the many CVEs in docker client dependencies.

I’d like to add org.mandas.docker.client and it’s updated set of dependencies to Orbit and update linux-tools Docker Tooling Support [5] to use it.

 

I updated create-docker-recipes.sh [6] to make a first pass at generating a recipe for this and it spit out a list of dependencies that will need recipes.

I took the list and compared with what is available in orbit and I’ll need to update 13 bundles and add 8 new bundles.

I’d like to add a README.md to the org.mandas.docker.client bundle which lists these dependencies and locations in orbit in order to ease maintenance going forward.

I’d like to land this set of changes for 2020-03.

 

Should I open 22 change requests (1 + 13 + 8), one giant change request for all of these changes or somewhere in between?


I would create one change per modified/new bundle
 

Should the obsolete Spotify Docker Client and/or it’s dependencies be removed from Orbit?


I'd remove obsolete bundle versions if you add newer one.
If some project still needs an old version they can still use it using an existing Orbit R-build.
 
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/orbit-dev

Back to the top