... | ... | @@ -192,17 +192,9 @@ to evolve independently without breaking other projects. |
|
|
|
|
|
For instance, a dependency to another {gecos} project <__pname2__> at version <__X.Y.Z__>
|
|
|
MUST be specified in the target definition file from its update site with the proper version number: +
|
|
|
<__siteURL__>/gecos/<__pname2__>/release/<__X.Y.Z__>/
|
|
|
|
|
|
WARNING: DO NOT use the latest version link !
|
|
|
This ensures that each project can safely evolve independently from other {gecos} projects without breaking other dependent projects.
|
|
|
|
|
|
To ensure to correct functionning, the new {gecos} update site structure must be handles with extreme cautiousness.
|
|
|
Always back it up before doing any manipulation.
|
|
|
Be careful in case you want to perform a restructuring of the update site, In this case you need to keep in mind and properly modify the target definition files of all projects.
|
|
|
|
|
|
<<section-update-site, Update site section>>
|
|
|
`<siteUR>/gecos/<pname2>/release/<X.Y.Z>/` (see <<section-update-site, Update site section>>)
|
|
|
|
|
|
WARNING: DO NOT use the "latest" version link for specifying dependencies !
|
|
|
|
|
|
|
|
|
|
... | ... | |