dotnet-installer/packaging/osx
Eric Mellino edbbc64b03 Fill out pkg installer targets
This causes three pkg files to be produced:

* A component pkg for the shared framework.
* A component pkg for the shared host.
* A product archive which includes the above two components.

The product archive also needs a distribution.xml file which contains
metadata about the package (name, title, images, etc.).

The installer for the "SDK" itself is still using logic implemented in
package-osx.sh. We should move this logic into the build target as well,
but we may want to wait until the CLI is using the shared framework to do so.
2016-03-10 10:31:45 -08:00
..
resources Responding to PR feedback pt. 2 2016-01-18 08:54:20 -08:00
scripts Moving PKG postinstall to use the path 2016-01-15 11:06:44 -08:00
sharedframework Fill out pkg installer targets 2016-03-10 10:31:45 -08:00
sharedhost/scripts Fill out pkg installer targets 2016-03-10 10:31:45 -08:00
Distribution-Template Add a custom conclusion file 2016-01-15 17:00:15 -08:00
package-osx.sh Address PR feedback and remove Azure CLI from dockerfiles 2016-03-08 18:46:54 -08:00