Skip to content

Archive buildiers should create an md5sums file #1057

@aiuto

Description

@aiuto

A common idiom for distribution packages is to have an outer shell with metadata, and an inner payload of a compressed archive of files to install. For example, a .deb package is

  • foo.deb
    • control.tar.gz
    • debian-binary
    • data.tar.xz

Where control.tar contains the metadata files and data.tar contains the payload. For .deb files, the metadata is

  • control - general info
  • md5sums - a list of every file in the payload with its md5 hash
  • install and uninstall scripts

Alternatives

  • We could read the tarball which is input to a .deb and compute the md5 file
  • We could have the tar writer calculate the sums and write them as an additional output
  • We could create a rule that takes pkg_* targets as inputs and calculates the md5.

The best choice is probably the first, because that is where we have built the map of sources to their destination paths. The md5 files would use destination paths.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions