Updates:
package
{
name: liba;
binding:1.0.0.0-{{$CURRENT-1}};
}
identity
{
file: foo.pfx;
pass: something;
}
sharedlib
{
policy-file:5.5;
policy-file:5.4;
}
assembly[liba.dll]
{
name: liba;
file: foo.dll;
file: bar.dll;
}
app
{
// recursive-include: ".\*";
include: "foo.exe" = ".\output\x86\release\bin\foo.exe";
include: "resources\**";
include: "foo\test.xyz" = "..\foo\test.xyz";
exclude: ".\foo.xyz";
exclude: ".\**\.bzr";
exclude: ".\test-*";
exclude: ".foo\**\*.txt";
}
exe-file[something.exe]
{
global-bin: true;
}
From: Eric Schultz [mailto:[email protected]]
Sent: Friday, April 22, 2011 5:00 PM
To: Garrett Serack; coapp-developers
Subject: Input for Autopackage
All,
The input to autopackage currently uses a very basic ini file format. While
very simple, it's a little difficult to describe certain things that way.
Garrett suggested using something along the lines of the format for his
cascading property sheets used in mkSpec. I quickly wrote up a simple example
on that and I thought I'd ask to see how people feel about this. I hope the
sample is self-explanatory-ish but if not, feel free to ask.
Eric
package
{
name: liba;
binding:1.0.0.0-{{$CURRENT-1}};
}
identity
{
file: foo.pfx;
pass: something;
}
sharedlib
{
policy-file:5.5;
policy-file:5.4;
}
assembly[liba.dll]
{
name: liba;
file: foo.dll;
file: bar.dll;
}
app
{
recursive: /*
}
exe-file[something.exe]
{
global-bin: true;
}
exe-file[foo.exe]{}
_______________________________________________
Mailing list: https://launchpad.net/~coapp-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
