| 1 |
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> |
| 2 |
<profile project="MinGW" application="mingw-get"> |
| 3 |
<!-- |
| 4 |
$Id: profile.xml,v ee72dbfcc656 2013/09/20 12:05:26 keithmarshall $ |
| 5 |
|
| 6 |
Written by Keith Marshall <keithmarshall@users.sourceforge.net> |
| 7 |
Copyright (C) 2009, 2010, 2012, 2013, MinGW.org 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 |
<preferences client="cli"> |
| 35 |
<!-- |
| 36 |
"preferences" specifications provide a mechanism for defining |
| 37 |
user specified default attributes for command line options such |
| 38 |
as the "desktop" and "start-menu" short-cut creation controls. |
| 39 |
|
| 40 |
Each of these options is disabled by default. By uncommenting |
| 41 |
any one of the following declarations, for each option, you may |
| 42 |
change that default. Note that you may still override settings |
| 43 |
you establish here, by also specifying the option on the command |
| 44 |
line as before; you may also disable an option enabled here, by |
| 45 |
assigning an attribute value of "none" on the command line. |
| 46 |
--> |
| 47 |
|
| 48 |
<!--option name="desktop" /--> |
| 49 |
<!--option name="desktop" value="all-users" /--> |
| 50 |
|
| 51 |
<!--option name="start-menu" /--> |
| 52 |
<!--option name="start-menu" value="all-users" /--> |
| 53 |
</preferences> |
| 54 |
|
| 55 |
<preferences client="gui"> |
| 56 |
<!-- |
| 57 |
The preceding "preferences" section applies exclusively to the |
| 58 |
CLI client, (where command line options may be used); here, we |
| 59 |
specify defaults for the GUI client, (which provides no support |
| 60 |
for command line options), such that shortcuts will be created |
| 61 |
on the desktop, and in the start menu, for the current user. |
| 62 |
|
| 63 |
Note that matching of the "client" attribute will be performed |
| 64 |
case-insensitively, against a keyword defined by the respective |
| 65 |
client; any "preferences" section with no "client" assignment |
| 66 |
will be matched for ALL clients. |
| 67 |
--> |
| 68 |
|
| 69 |
<option name="desktop" /> |
| 70 |
<option name="start-menu" /> |
| 71 |
</preferences> |
| 72 |
|
| 73 |
<repository uri="http://prdownloads.sourceforge.net/mingw/%F.xml.lzma?download"> |
| 74 |
<!-- |
| 75 |
The "repository" specification identifies the URI where package |
| 76 |
list catalogues may be downloaded; each catalogue download URI is |
| 77 |
identified by substituting the catalogue name for the "%F" field |
| 78 |
in the uri specification. |
| 79 |
|
| 80 |
You may specify a particular collection of package lists to load |
| 81 |
here, (selecting from the available catalogue-name.xml.lzma files |
| 82 |
hosted on the repository server). If you do this, then ONLY those |
| 83 |
package lists which you explicitly specify will be loaded. If you |
| 84 |
specify no package list here, then the repository's standard list |
| 85 |
of packages, as identified in the master "package-list.xml.lzma" |
| 86 |
file will be automatically selected; this is the recommended |
| 87 |
configuration choice. |
| 88 |
|
| 89 |
Note however, that if the repository offers optional package list |
| 90 |
selections, in addition to the the master list, and you wish any of |
| 91 |
these to be loaded, then you MUST explicitly specify them here. If |
| 92 |
you exercise this option, then the automatic loading of the master |
| 93 |
list will be inhibited, UNLESS you also explicitly include it in |
| 94 |
your selection, by adding the explicit reference:- |
| 95 |
|
| 96 |
<package-list catalogue="package-list" /> |
| 97 |
|
| 98 |
Additional package lists, which you wish to specify, are then |
| 99 |
identified by the addition of as many further references of the |
| 100 |
form:- |
| 101 |
|
| 102 |
<package-list catalogue="catalogue-name" /> |
| 103 |
|
| 104 |
as may be required; (note that the "catalogue" attribute name |
| 105 |
MUST be specified thus, with the GB English spelling). |
| 106 |
--> |
| 107 |
</repository> |
| 108 |
|
| 109 |
<system-map id="default"> |
| 110 |
<!-- |
| 111 |
The system map specifies the installation paths for each managed |
| 112 |
subsystem. Multiple system maps are supported, provided each is |
| 113 |
given a unique "id" attribute; each specifies an "installation", |
| 114 |
comprising a collection of subsystems, each of which in turn is |
| 115 |
associated with a specific "sysroot path". |
| 116 |
|
| 117 |
Each individual "sysroot path" defines one installation of one |
| 118 |
specific subsystem; parallel installations may be supported by |
| 119 |
assigning distinct paths to two or more sysroot specifications |
| 120 |
for the same subsystem; each such sysroot specification must |
| 121 |
then be assigned to a distinct system-map. |
| 122 |
|
| 123 |
Any single sysroot definition may be shared by any number of |
| 124 |
system-maps, simply by duplicating that definition within each; |
| 125 |
however, each system-map may contain only one sysroot definition |
| 126 |
for each individual subsystem. |
| 127 |
|
| 128 |
Only one system map may be active at any time. Unless otherwise |
| 129 |
specified by user selection, the first encountered is accepted as |
| 130 |
default, irrespective of its actual "id" attribute value. |
| 131 |
--> |
| 132 |
<sysroot subsystem="mingw32" path="%R" /> |
| 133 |
<sysroot subsystem="MSYS" path="%R/msys/1.0" /> |
| 134 |
</system-map> |
| 135 |
|
| 136 |
</profile> |
| 137 |
<!-- $RCSfile: profile.xml,v $: end of file --> |
