Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Selective minversion capability #89

Open
phmccarty opened this issue Oct 10, 2017 · 3 comments
Open

Selective minversion capability #89

phmccarty opened this issue Oct 10, 2017 · 3 comments

Comments

@phmccarty
Copy link
Contributor

phmccarty commented Oct 10, 2017

swupd_create_update supports a "minversion" feature that forces regeneration of update content that last changed prior to a given version.

A variation of this feature would be to only regenerate content that last changed in a selected version. In other words, for build CURRENT_VERSION, instead of regenerating all content with last_change < MIN_VERSION, only regenerate content with last_change == MIN_VERSION. The regenerated content will have last_change CURRENT_VERSION, same as the "minversion" feature behavior.

@matthewrsj
Copy link
Contributor

Why? In the case of a bad release?

@matthewrsj
Copy link
Contributor

Trying to determine if this is an issue we should open against mixer.

@phmccarty
Copy link
Contributor Author

Why? In the case of a bad release?

Yes, in case there is a bad release in the middle of an update stream of otherwise good releases, we could selectively rebuild files that last changed at that bad version.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants