-
Notifications
You must be signed in to change notification settings - Fork 24
Include and exclude in Autopackage
Include and exclude properties are used in a number of properties for Autopackage input files. These include:
###Wildcards Include and exclude properties both use wildcards. CoApp wildcards are very similar to wildcards used in Windows and the .NET Framework. The major difference is in the exact meaning of * in a wildcard.
In a Windows wildcard, an * can match any character in a file path, very similar to .* in Perl-compatible
regular expressions. For example, foo\*.bar
could match foo\baz.bar
and foo\test\baz.bar
. Similarly,
foo\*
could match foo\baz.bar
and foo\test\baz.bar
.
In a CoApp wildcard, an * will not match path separator characters (\ or /). This means using CoApp wildcards
foo\*.bar
will match foo\baz.bar
but NOT foo\test\baz.bar
and foo\*
will match
foo\baz.bar
but NOT foo\test\baz.bar
. One could say that, in CoApp wildcards * does not cross
directory boundaries.
In order to cross a directory boundary, CoApp wildcards use **. For example foo\**
will match foo\baz.bar
and foo\test\baz.bar
. It is important to note that ** must be in it's own path section. In other words,
foo\**.bar
is invalid. On the other hand, foo\**\*.bar
is valid and will match foo\baz.bar
and
foo\test\baz.bar
.
###Include Include properties can come in a few different forms.
The first form is as a compound value. An include that a compound value would look like:
include: "foo\bar"="input\directory\*"
What this means is every input file captured by the first wildcard, will be put into the foo\bar
subdirectory of the
output directory. When the package is installed the files the input\directory\baz.txt
will be placed into
<output dir>\foo\bar\baz.txt
.
Additionally if the