Skip to content

Baseset releases should have metadata made available to reproduce builds #112

@kaechele

Description

@kaechele

After #96 no source bundles are created or uploaded any more.

With that, distributions such as Debian and Fedora, that have requirements to build packages from source, no longer have a convenient way to rebuild a baseset from source.

There are a few methods to work around this:

  1. Use the git repo directly
    At least for me as the Fedora maintainer of OpenGFX this adds a few steps I have to perform for each release, as builds happen offline and I can't clone the git repo in the build system.
    I have a few options:

    1. Ship my own copy of the repo contents and add git to my BuildRequires.
    2. Ship a script in the package source repo that needs to be run before rolling a new release: clone the repo, run a build to generate .ottdrev, then download the official release to extract opengfx-8.0.check.md5 from opengfx.obg. Put these files in the package source repo and commit them.
  2. Ship .ottdrev and opengfx-8.0.check.md5 as release artifacts
    Either inside the binary release or as separate files to the release.
    Saves me the script from 1 (ii) above. I could download these from the release artifacts and commit them to package source.

For OpenGFX specifically (I haven't check OpenGFX2) we could also think about changing the way the Makefile receives its version information. It could be added that the required information can be parsed from the obg of the original release and that then being provided raw with the release artifacts.

Let me know your thoughts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions