Revision 922

trunk/utilities/mingw/var/lib/mingw-get/data/profile.xml (revision 922)
1
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
2
<profile project="MinGW" application="mingw-get">
3
  <!--
4
    $Id: profile.xml,v 1.4 2010/08/24 20:02:10 keithmarshall Exp $
5

  
6
    Written by Keith Marshall  <keithmarshall@users.sourceforge.net>
7
    Copyright (C) 2009, 2010, MinGW Project
8

  
9

  
10
    Master configuration profile for mingw-get.
11

  
12
    This file is user modifiable, to accommodate local customisation
13
    of mingw-get's behaviour.  To avoid overwriting the user's local
14
    customisations, when upgrading the mingw-get installation, this
15
    file is distributed with the alternative name "defaults.xml"; a
16
    locally customised version should always be renamed, so that it
17
    may be identified as the preferentially loaded "profile.xml".
18

  
19

  
20
    This is free software.  Permission is granted to copy, modify and
21
    redistribute this software, under the provisions of the GNU General
22
    Public License, Version 3, (or, at your option, any later version),
23
    as published by the Free Software Foundation; see the file COPYING
24
    for licensing details.
25

  
26
    Note, in particular, that this software is provided "as is", in the
27
    hope that it may prove useful, but WITHOUT WARRANTY OF ANY KIND; not
28
    even an implied WARRANTY OF MERCHANTABILITY, nor of FITNESS FOR ANY
29
    PARTICULAR PURPOSE.  Under no circumstances will the author, or the
30
    MinGW Project, accept liability for any damages, however caused,
31
    arising from the use of this software.
32
  -->
33

  
34
  <repository uri="http://prdownloads.sourceforge.net/mingw/%F.xml.lzma?download">
35
    <!--
36
      The "repository" specification identifies the URI where package
37
      list catalogues may be downloaded; each catalogue download URI is
38
      identified by substituting the catalogue name for the "%F" field
39
      in the uri specification.
40

  
41
      You may specify a particular collection of package lists to load
42
      here, (selecting from the available catalogue-name.xml.lzma files
43
      hosted on the repository server).  If you do this, then ONLY those
44
      package lists which you explicitly specify will be loaded.  If you
45
      specify no package list here, then the repository's standard list
46
      of packages, as identified in the master "package-list.xml.lzma"
47
      file will be automatically selected; this is the recommended
48
      configuration choice.
49

  
50
      Note however, that if the repository offers optional package list
51
      selections, in addition to the the master list, and you wish any of
52
      these to be loaded, then you MUST explicitly specify them here.  If
53
      you exercise this option, then the automatic loading of the master
54
      list will be inhibited, UNLESS you also explicitly include it in
55
      your selection, by adding the explicit reference:-
56

  
57
	<package-list catalogue="package-list" />
58

  
59
      Additional package lists, which you wish to specify, are then
60
      identified by the addition of as many further references of the
61
      form:-
62

  
63
	<package-list catalogue="catalogue-name" />
64

  
65
      as may be required; (note that the "catalogue" attribute name
66
      MUST be specified thus, with the GB English spelling).
67
    -->
68
  </repository>
69

  
70
  <system-map id="default">
71
    <!--
72
      The system map specifies the installation paths for each managed
73
      subsystem.  Multiple system maps are supported, provided each is
74
      given a unique "id" attribute; each specifies an "installation",
75
      comprising a collection of subsystems, each of which in turn is
76
      associated with a specific "sysroot path".
77
      
78
      Each individual "sysroot path" defines one installation of one
79
      specific subsystem; parallel installations may be supported by
80
      assigning distinct paths to two or more sysroot specifications
81
      for the same subsystem; each such sysroot specification must
82
      then be assigned to a distinct system-map.
83

  
84
      Any single sysroot definition may be shared by any number of
85
      system-maps, simply by duplicating that definition within each;
86
      however, each system-map may contain only one sysroot definition
... This diff was truncated because it exceeds the maximum size that can be displayed.

Also available in: Unified diff