Can these patches be considered again for 20.08? I thought that I addressed all of the issues or at least provided reasonable responses to all of the concerns.
thanks dan On Mon, May 4, 2020 at 11:19 AM Dan Gora <d...@adax.com> wrote: > > On Mon, May 4, 2020 at 11:13 AM Dan Gora <d...@adax.com> wrote: > > > > On Mon, May 4, 2020 at 5:04 AM Mattias Rönnblom > > <mattias.ronnb...@ericsson.com> wrote: > > > > > >> so what you are effectively asking is to > > > >> double the size of the support matrix, and for the project to ensure > > > >> that every single dependency can always be built against a new version > > > >> and used against an older one. > > > > No, this is not correct. The size of the support/test matrix is > > > > exactly the same, what changes is the number of build systems that > > > > have to be supported. > > > > > > > > Before my patches you had to test targets with: > > > > > > > > no rdseed and no getentropy > > > > rdseed and no getentropy > > > > no rdseed and getentropy > > > > rdseed and getentropy. > > > > > > > > > rdseed will go away eventually, when all reasonable systems have > > > getentropy(). That might well take a couple of years. > > So then why not just use only /dev/urandom for now, then change DPDK > to use getentropy() when "all reasonable systems have getentropy()"? > > *problem solved* > > thanks > dan
