<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<!--
  What the installer offers, which is nothing to choose.

  One component, no options, and the system volume only: a NAC agent installed
  into a home directory would be an agent an administrator cannot see and cannot
  be sure is there, which is the opposite of what this product is for.

  hostArchitectures names both because the binary inside is universal - the
  fleet has Apple silicon and Intel Macs in it, and one package for both is one
  thing to sign, notarise, checksum and roll out.

  0.0.11 and component.pkg are filled in by build.sh.
-->
<installer-gui-script minSpecVersion="2">
    <title>Exordos NAC Agent</title>
    <options customize="never" require-scripts="false" hostArchitectures="arm64,x86_64"/>
    <volume-check>
        <allowed-os-versions>
            <os-version min="13.0"/>
        </allowed-os-versions>
    </volume-check>
    <domains enable_anywhere="false" enable_currentUserHome="false" enable_localSystem="true"/>
    <choices-outline>
        <line choice="default">
            <line choice="io.exordos.nac.agent"/>
        </line>
    </choices-outline>
    <choice id="default"/>
    <choice id="io.exordos.nac.agent" visible="false">
        <pkg-ref id="io.exordos.nac.agent"/>
    </choice>
    <pkg-ref id="io.exordos.nac.agent" version="0.0.11" onConclusion="none" installKBytes="15491" updateKBytes="0">#component.pkg</pkg-ref>
    <pkg-ref id="io.exordos.nac.agent">
        <bundle-version>
            <bundle CFBundleShortVersionString="0.0.11" CFBundleVersion="0.0.11" id="io.exordos.nac" path="Library/Application Support/exordos_nac/Exordos NAC Agent.app"/>
        </bundle-version>
    </pkg-ref>
</installer-gui-script>