Update coreutils replacement after feedback

Update concept document about coreutils replacement based on feedback

• Add license information for dependencies
• Include reference for both APT and OSTree images
• Minor typos

content/concepts/coreutils-replacement.md

@@ -212,6 +212,70 @@ Based on the above comparison the best option is `uutils-coreutils`, since it is
 
 These risks enumerated will be handled by the testing and migration in order to provide a reliable approach.
 
+As it has been mentioned the license used is MIT, and detailed information about its dependencies can be found in the
+[FOSSA analysis](https://app.fossa.io/projects/git%2Bgithub.com%2Fuutils%2Fcoreutils?ref=badge_large"). Unfortunately, this report is not reliable since it shows several incorrect dependencies.
+
+The following list shows the dependencies as reported by `cargo`
+
+| Package             | License              |
+|---------------------|----------------------|
+|ansi_term            | MIT                  |
+|arrayvec             | MIT/Apache-2.0       |
+|autocfg              | Apache-2.0/MIT       |
+|backtrace-sys        | MIT/Apache-2.0       |
+|bitflags             | MIT/Apache-2.0       |
+|bit-set              | MIT/Apache-2.0       |
+|bit-vec              | MIT/Apache-2.0       |
+|blake2-rfc           | MIT OR Apache-2.0    |
+|byteorder            | Unlicense OR MIT     |
+|cfg-if               | MIT/Apache-2.0       |
+|chrono               | MIT/Apache-2.0       |
+|constant_time_eq     | CC0-1.0              |
+|data-encoding        | MIT                  |
+|dunce                | CC0-1.0              |
+|either               | MIT/Apache-2.0       |
+|failure              | MIT OR Apache-2.0    |
+|fake-simd            | MIT/Apache-2.0       |
+|fnv                  | Apache-2.0 / MIT     |
+|fs_extra             | MIT                  |
+|glob                 | MIT/Apache-2.0       |
+|half                 | MIT/Apache-2.0       |
+|hex                  | MIT OR Apache-2.0    |
+|ioctl-sys            | MIT OR Apache-2.0    |
+|isatty               | MIT/Apache-2.0       |
+|maybe-uninit         | Apache-2.0 OR MIT    |
+|md5                  | Apache-2.0/MIT       |
+|num-integer          | MIT OR Apache-2.0    |
+|onig                 | MIT                  |
+|onig_sys             | MIT                  |
+|pkg-config           | MIT/Apache-2.0       |
+|platform-info        | MIT                  |
+|ppv-lite86           | MIT/Apache-2.0       |
+|rand_chacha          | MIT OR Apache-2.0    |
+|rand_pcg             | MIT OR Apache-2.0    |
+|rust-ini             | MIT                  |
+|semver               | MIT/Apache-2.0       |
+|semver-parser        | MIT/Apache-2.0       |
+|sha1                 | BSD-3-Clause         |
+|sha2                 | MIT/Apache-2.0       |
+|sha3                 | MIT/Apache-2.0       |
+|smallvec             | MIT/Apache-2.0       |
+|strsim               | MIT                  |
+|syn                  | MIT OR Apache-2.0    |
+|synom                | MIT/Apache-2.0       |
+|synstructure         | MIT                  |
+|tempfile             | MIT OR Apache-2.0    |
+|term_grid            | MIT                  |
+|termsize             | MIT                  |
+|term_size            | MIT/Apache-2.0       |
+|thread_local         | Apache-2.0/MIT       |
+|typenum              | MIT/Apache-2.0       |
+|unix_socket          | MIT/Apache-2.0       |
+|vec_map              | MIT/Apache-2.0       |
+|wild                 | Apache-2.0 OR MIT    |
+|winapi-util          | Unlicense/MIT        |
+|xattr                | MIT/Apache-2.0       |
+
 # Testing
 In order to confirm the missing features/commands in the `uutils-coreutils` which are required by Apertis a testing needs to be performed. The steps proposed are:
 
@@ -220,7 +284,7 @@ In order to confirm the missing features/commands in the `uutils-coreutils` whic
   - Test installing/removing packages
 - Run current `coreutils-gplv2` test plan with `uutils-coreutils`
 - Run `uutils-coreutils` as default on development environments
-- Make `uuutils-coreutils` and all the Rust crates it depends on available in Debian
+- Make `uutils-coreutils` and all the Rust crates it depends on available in Debian
 - Provide long-term maintenance of the new packages in Debian as well  
 Note that some effort is being driven by `uutils-coreutils` community to use the `coreutils` test case to generate a report for the still missing features. This will be a nice to have feature but it is more than it is actually required for this stage.
 
@@ -242,5 +306,6 @@ The following guidelines will be followed to assure a smooth transition minimizi
 - Determine the list of tools supported and successfully tested provided by `uutils-coreutils`.
 - Create a new package based on `uutils-coreutils` named `coreutils-uutils` with all the tools that are supported and successfully tested.
 - For missing tools a replacement will be provided on case by case basis.
+- Generate APT and OSTree based images for target and minimal configuration.
 
 Due to the [Apertis release flow]( {{< ref "release-flow.md" >}} ) this process will start on development releases allowing any potential issue to be addressed before a stable point release, with the possibility of switching back to `coreutils-gplv2` if a proper fix cannot be implemented on time.