1,574
edits
Changes
Jump to navigation
Jump to search
Line 178:
Line 178: − + + + + + + +
→DEALING WITH PACKAGE DEPENDENCIES.
The verification phase taking place before release should pick up hard dependencies which could break an update. What needs to be checked is where a package fixes three bugs and one was not verified. That means that only an older version of that package can be released. Also it can affect other packages if one of the fixes involved multiple packages. Note that the 'Verified Package Versions' tab in Rnotes will track this - it does what Ian used to do normally and try to build a bug and package dependency graph.
The verification phase taking place before release should pick up hard dependencies which could break an update. What needs to be checked is where a package fixes three bugs and one was not verified. That means that only an older version of that package can be released. Also it can affect other packages if one of the fixes involved multiple packages. Note that the 'Verified Package Versions' tab in Rnotes will track this - it does what Ian used to do normally and try to build a bug and package dependency graph.
We can distinghish between "hard" and "soft" dependencies referred to in this document as follows
We can distinghish between "hard" and "soft" dependencies referred to in this document as follows:
:a) Hard dependencies are those from the spec file, eg: requires: e-smith-lib >= 2.0.0-2
Developers put these when it is necessary to enforce dependencies between packages.
:b) Soft dependencies relates to package dependencies setup in Bugzilla.
As an illustration, consider the following scenario, actual bug numbers etc are made up for this example: