1. 16 May, 2022 1 commit
  2. 28 Apr, 2022 1 commit
  3. 21 Apr, 2022 1 commit
    • Ryan Gonzalez's avatar
      Properly resolve full license information for Rust binaries · e5a81d3f
      Ryan Gonzalez authored
      There are two primary issues when applying the current mechanisms for
      tracking source file licensing information to Rust binaries:
      
      - They statically link in their crate dependencies, meaning that we
        need to manually include the licenses of those crates
      - The compilation unit paths only include the primary "entry point"
        into the crate, and they're a mix of absolute and relative paths
      
      In order to resolve this:
      
      - pkg/debhelper!18 will
        gather the license information for any source files referenced that
        are part of other packages. We can read this in here and use it to
        search the copyright information for the source files part of other
        crates.
      - Specifically when encountering Rust crates, combine all the licenses
        for source files within the same source directory as the "entry point"
        file, which should generally ensure that all the source files needed
        are handled.
      
      As the amount of information that needs to be held per package has
      increased drastically, a new PackageLicenseInfo class was introduced,
      encapsulating the primary copyright, external copyrights, external
      sources index, and the bin2sources data.
      
      https://phabricator.apertis.org/T8554
      
      This should also, specifically for Rust, resolve the spin-off issues:
      
      https://phabricator.apertis.org/T8776
      https://phabricator.apertis.org/T8777
      
      Signed-off-by: Ryan Gonzalez's avatarRyan Gonzalez <ryan.gonzalez@collabora.com>
      e5a81d3f
  4. 20 Apr, 2022 2 commits
    • Walter Lozano's avatar
      generate_bom: Do not scan recursively · c7012de3
      Walter Lozano authored
      
      
      During BOM file generation, a folder with a sub folder per package is
      scanned to process the copyright information. With this folder
      structure in mind, there is no need to make a recursive scan,
      so simplify the implementation to avoid misleading warnings.
      Signed-off-by: Walter Lozano's avatarWalter Lozano <walter.lozano@collabora.com>
      c7012de3
    • Walter Lozano's avatar
      genarate_bom: Improve generation with smart check for licenses · bc550126
      Walter Lozano authored
      
      
      The current process to generate the BOM file relies on determine the
      license of the source files reported by dwarf2sources. Unfortunately
      there are several trickiness with this.
      
      First, depending on the build system used and debian rules the values
      reported by dwarf2source might not match the source tree. Also the
      license scan tool tends to used wildcards which make the search of a
      file with the wrong path not to fail but to report the default license.
      
      In order to properly fix a more strict approach should be use, as a first
      step in that direction, improve the BOM generation by trying to guess
      the path_prefix to be appended to the source file as reported by
      dwarf2souces to match the source tree.
      Signed-off-by: Walter Lozano's avatarWalter Lozano <walter.lozano@collabora.com>
      bc550126
  5. 19 Apr, 2022 1 commit
  6. 31 Mar, 2022 2 commits
  7. 30 Mar, 2022 2 commits
  8. 11 Mar, 2022 2 commits
  9. 08 Mar, 2022 2 commits
  10. 17 Feb, 2022 2 commits
  11. 15 Feb, 2022 2 commits
  12. 14 Feb, 2022 1 commit
  13. 10 Feb, 2022 1 commit
  14. 07 Feb, 2022 1 commit
  15. 03 Feb, 2022 1 commit
  16. 02 Feb, 2022 1 commit
  17. 28 Jan, 2022 1 commit
  18. 27 Jan, 2022 1 commit
  19. 17 Jan, 2022 1 commit
  20. 04 Jan, 2022 5 commits
  21. 03 Jan, 2022 2 commits
  22. 30 Dec, 2021 1 commit
  23. 24 Dec, 2021 1 commit
  24. 23 Dec, 2021 1 commit
  25. 21 Dec, 2021 1 commit
  26. 15 Dec, 2021 1 commit
  27. 10 Dec, 2021 1 commit
  28. 05 Dec, 2021 1 commit