branches: add revision and mandatory to changes #404
Conversation
The revision can be used to "date" package changes so that updates between i.e. snapshots won't be suggested every time. The mandatory field is used to specify if a changes is selectable or not. If a package is dropped, the changes will always be selected. Signed-off-by: Paul Spooren <paul.spooren@rhebo.com>
Codecov ReportBase: 85.08% // Head: 85.08% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #404 +/- ##
=======================================
Coverage 85.08% 85.08%
=======================================
Files 13 13
Lines 1153 1153
=======================================
Hits 981 981
Misses 172 172 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
A package which should be dropped optionally is also an imaginable situation, let's say e.g. in future we decide to ditch uclient-fetch in favor of yet another wget implenentation we would also drop libustream-wolfssl from the default package set. In that case, the package is dropped, but the user should have the option to keep it (as it is still present as a package in the tree, it's just no longer part of the default set and has been replaced there). |
| mandatory: true | ||
| - source: firewall | ||
| target: firewall4 | ||
| revision: 18611 |
There was a problem hiding this comment.
As both changes (firewall -> firewall4, kmod-nft-nat6 -> null) are present already in the 22.03 release branch, why do you list them again in SNAPSHOT? That makes it much harder for the client to decide which changes to include...
The revision can be used to "date" package changes so that updates between i.e. snapshots won't be suggested every time.
The mandatory field is used to specify if a changes is selectable or not. If a package is dropped, the changes will always be selected.
Signed-off-by: Paul Spooren paul.spooren@rhebo.com