...
- Existing packages are not modified.
- For each product-productversion at most one new + version is introduced, even if several changes have to be applied to it.
- Newly introduced + versions are copies of the previous + versions. The only changes are applied to the table files (
setupRequired(..)entries ) to reflect changes in the dependencies. - No new dependencies are added, nor are dependencies removed. They may be replaced by different versions.
Dependency Updater
Running The Dependency Updater
The typical user scenario looks as follows: Create a new version of a given 'reference' package by replacing one or several of its direct or indirect dependencies by a new version.
Let's do a specific example - actually an artificial example to increase the chance that this will never be added to the system so that you can always follow the steps (PLEASE: Skip the commit step in the end!).give a hypothetical example. Assume that you would like to to create a new diffimg version by replacing in diffimg-8.0.28+2 the indirect dependency python-2.7.6+1 by the updated version python-2.7.7+0. This will assume that you have already added python-2.7.7+0 into the system (which is not at the time of writing). Then you can run the following command:
...