On Wed, Oct 23, 2019 at 12:30:52PM -0600, Stephen Warren wrote:
On 10/22/19 9:20 PM, Tom Rini wrote:
To be more closely aligned with Python community best practices, we need to better document our usage of pip and make use of a requirements.txt file that shows the versions of the tools that we are using. This will aide in ensuring reproducibility of our tests as well.
+In order to execute certain tests on their supported platforms other tools +will be required. The following is an incomplete list:
+| Package | +| -------------- | +| gdisk | +| dfu-util | +| dtc |
This looks like my bug from before, but may as well fix it: That package doesn't exist, at least on Ubuntu 16.04. There is device-tree-compiler though.
I wonder how best to list that. Upstream is "dtc" and I forget what it's called package-wise on Fedora systems and similar. But since I want to avoid making a distribution specific list maybe I need to add a few words to be clear it's a tool list and not a package list. Doing "apt-cache search dtc" shows device-tree-compiler for example and I bet the dnf equivalent does too.
+| openssl | +| sudo OR guestmount |
Note that for example guestmount comes from libguestfs-tools on Debian/similar systems.
+| e2fsprogs | +| dosfstools | +| openssl |
openssl is listed twice.
Thanks, fixed.