On 21/04/12 17:17, Earnie Boyd wrote:
> On Fri, Apr 20, 2012 at 4:27 PM, Keith Marshall
> <keithmarshall@...> wrote:
>> I'm thinking primarily of options such as --desktop and --start-menu,
>> (added in mingw-get-0.5), for which users may wish to establish their
>> own preferred default settings. To accommodate this, I propose to add
>> handling for a <preferences>...</preferences> section in profile.xml
>> The implementation will ensure that any option specified on the command
>> line will override a default setting in profile.xml
>> I'd welcome your thoughts on preferred syntax for the XML; which of the
>> following would you prefer?
>> <set option="desktop" class="all-users" />
> This sounds a bit natural.
Which would be okay, right? Or did you mean unnatural?
>> <option name="desktop" value="all-users" />
> <preference desktop="all-users" />
> <preference start="mingw" />
This would not lend itself well to the implementation.
> Since we have preferences we should have a preference.
Having played a bit with implementation, I'm now leaning toward:
<enable option="desktop" [value="all-users"] />
<enable option="start-menu" [value="all-users"] />
<enable option="desktop" [preferences="all-users"] />
<enable option="start-menu" [preferences="all-users"] />
where the general form of the "enable" tag would be:
<enable option="option-name" [preferences="attribute[,...]] />
Not a big deal, I guess, but using the same spelling of the keyword
"preferences" for both the container element tag, and for the attribute
name, saves defining both the singular and plural forms as independent
The idea, for now, is to relieve users of the need to specify the
--desktop[=all-users] and the --start-menu[=all-users] command line
options, (see 'mingw-get --help' for the mingw-get-0.5-beta release), if
they would prefer to always allow post-install hooks to create
the associated short-cuts.