Changes between Version 6 and Version 7 of Obsolete/Doc/SCDB/SWRepositories
- Timestamp:
- Sep 18, 2006, 9:01:23 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Obsolete/Doc/SCDB/SWRepositories
v6 v7 30 30 === Associated Templates === 31 31 32 `PAN` need to know about repositories contents to be able to check if required packages are available at compile time. Thus for each software repository, there is an associated ''structure'' template describing the packages available in the repository. For PAN to know about repository content changes, the template `must` be updated. This is done with `ant`, SCDB management tool.32 `PAN` need to know about repositories contents to be able to check if required packages are available at compile time. Thus for each software repository, there is an associated ''structure'' template describing the packages available in the repository. For PAN to know about repository content changes, the template `must` be [wiki:Doc/SCDB/SWRepositories#UpdatingRPMRepositories updated]. This is done with `ant`, SCDB management tool. 33 33 34 34 Generally, templates associated with software repositories are grouped in one directory of SCDB. Recommandation is to put them in a directory called `repository` in your `site` sub-directory. e.g. [source:templates/trunk/sites/example/repository cfg/sites/example/repository]. … … 56 56 In every case, the management operations required are the same : 57 57 * Update of directory contents for the repository 58 * If this is a new repository, creation of associated template58 * If this is a new repository, [wiki:Doc/SCDB/SWRepositories#AssociatedTemplates creation of associated template]. 59 59 * Update of associated templates for all existing repositories. This done with `ant` tool, using `update.rep.templates` task. For this, you need to have a valid working copy of your SCDB. The command to execute is : 60 60 {{{