Difference between revisions of "Profiles.xml:French"
| Line 1: | Line 1: | ||
| − | + | '''profiles.xml''' is a file which defines the software packages or scripts, which will be installed/executed on hosts. | |
| + | |||
| + | This file has to be placed in the same direstory as [[wpkg.js]]. | ||
| + | |||
| + | [http://wpkg.org WPKG] will not work without this file. | ||
| + | |||
| + | Hosts are defined in [[hosts.xml]] file.<br> | ||
| + | Packages are defined in [[packages.xml]] file. | ||
| + | |||
| + | |||
| + | ==profiles.xml structure== | ||
| + | |||
| + | The structure of '''profiles.xml''' is as follows: | ||
| + | |||
| + | <blockquote style="background: white; border: 1px solid black; padding: 1em;"> | ||
| + | <profiles><br><br> | ||
| + | <profile id="'''default'''"><br> | ||
| + | <package package-id="'''acrobat'''" /><br> | ||
| + | <package package-id="'''firefox'''" /><br> | ||
| + | </profile><br><br> | ||
| + | <profile id="'''custom'''"><br> | ||
| + | <depends profile-id="'''default'''" /><br> | ||
| + | <package package-id="'''thunderbird'''" /><br> | ||
| + | </profile><br><br> | ||
| + | </profiles><br> | ||
| + | </blockquote> | ||
| + | |||
| + | Which means, that if a host, defined in [[hosts.xml]] has a profile '''default''' (the first profile above), it will have '''acrobat''' and '''firefox''' installed - because '''profile id="default"''' contains these two packages. | ||
| + | |||
| + | Now take a look at '''<depends profile-id="default" />''' entry in the next profile - '''<profile id="custom">'''.<br> | ||
| + | This profile only seems to contain a '''thunderbird''' package.<br> | ||
| + | But because it ''depends'' on '''<profile id="default">''', which contains two more packages ('''acrobat''' and '''firefox''') - it all sums up, and in the end, a host with a profile '''custom''' will have three packages installed: '''acrobat''', '''firefox''' and '''thunderbird'''. | ||
| + | |||
| + | |||
| + | This way you can easily create a group of packages to be installed on all workstations (for example, in profile '''default'''), and then create specific profiles for different rooms, departments etc. | ||
| + | |||
| + | Profiles can depend on more than one package. | ||
| + | |||
| + | ==Quick examples== | ||
| + | |||
| + | <blockquote style="background: white; border: 1px solid black; padding: 1em;"> | ||
| + | <profiles><br><br> | ||
| + | <profile id="default"><br> | ||
| + | <package package-id="firefox" /><br> | ||
| + | </profile><br> | ||
| + | <br> | ||
| + | <profile id="custom"><br> | ||
| + | <depends profile-id="default" /><br> | ||
| + | <package package-id="thunderbird" /><br> | ||
| + | <package package-id="acrobat" /><br> | ||
| + | </profile><br> | ||
| + | <br> | ||
| + | <profile id="basement"><br> | ||
| + | <package package-id="photoshop" /><br> | ||
| + | </profile><br> | ||
| + | <br> | ||
| + | <profile id="administration"><br> | ||
| + | <depends profile-id="custom" /><br> | ||
| + | <package package-id="firefox" /><br> | ||
| + | <package package-id="database" /><br> | ||
| + | </profile><br> | ||
| + | <br> | ||
| + | </profiles><br> | ||
| + | </blockquote> | ||
| + | |||
| + | ==See also== | ||
| + | * [[hosts.xml]] - defines the hosts. | ||
| + | * [[packages.xml]] - defines the list of packages. | ||
| + | * [[wpkg.js]] - WPKG engine. | ||
| + | |||
| + | [[category:Documentation]] | ||
| + | [[category:Installation]] | ||
| + | [[category:Config_Files]] | ||
Revision as of 16:21, 26 June 2007
profiles.xml is a file which defines the software packages or scripts, which will be installed/executed on hosts.
This file has to be placed in the same direstory as wpkg.js.
WPKG will not work without this file.
Hosts are defined in hosts.xml file.
Packages are defined in packages.xml file.
profiles.xml structure
The structure of profiles.xml is as follows:
<profiles>
<profile id="default">
<package package-id="acrobat" />
<package package-id="firefox" />
</profile>
<profile id="custom">
<depends profile-id="default" />
<package package-id="thunderbird" />
</profile>
</profiles>
Which means, that if a host, defined in hosts.xml has a profile default (the first profile above), it will have acrobat and firefox installed - because profile id="default" contains these two packages.
Now take a look at <depends profile-id="default" /> entry in the next profile - <profile id="custom">.
This profile only seems to contain a thunderbird package.
But because it depends on <profile id="default">, which contains two more packages (acrobat and firefox) - it all sums up, and in the end, a host with a profile custom will have three packages installed: acrobat, firefox and thunderbird.
This way you can easily create a group of packages to be installed on all workstations (for example, in profile default), and then create specific profiles for different rooms, departments etc.
Profiles can depend on more than one package.
Quick examples
<profiles>
<profile id="default">
<package package-id="firefox" />
</profile>
<profile id="custom">
<depends profile-id="default" />
<package package-id="thunderbird" />
<package package-id="acrobat" />
</profile>
<profile id="basement">
<package package-id="photoshop" />
</profile>
<profile id="administration">
<depends profile-id="custom" />
<package package-id="firefox" />
<package package-id="database" />
</profile>
</profiles>
See also
- hosts.xml - defines the hosts.
- packages.xml - defines the list of packages.
- wpkg.js - WPKG engine.