dotnet-installer/packaging/osx/sharedhost/scripts/postinstall

#!/bin/sh
#
# Copyright (c) .NET Foundation and contributors. All rights reserved.
# Licensed under the MIT license. See LICENSE file in the project root for full license information.
#

PACKAGE=$1
INSTALL_DESTINATION=$2

# A temporary fix for the permissions issue(s)
chmod 755 $INSTALL_DESTINATION/dotnet

# Add the installation directory to the system-wide paths
echo $INSTALL_DESTINATION | tee -a /etc/paths.d/dotnet

exit 0
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-09 21:26:37 +00:00			`#!/bin/sh`
			`#`
			`# Copyright (c) .NET Foundation and contributors. All rights reserved.`
			`# Licensed under the MIT license. See LICENSE file in the project root for full license information.`
			`#`

			`PACKAGE=$1`
			`INSTALL_DESTINATION=$2`

			`# A temporary fix for the permissions issue(s)`
			`chmod 755 $INSTALL_DESTINATION/dotnet`

Add to $PATH in the .Net Core Host pkg Earlier it was incorrectly done in .Net CLI pkg 2016-03-25 18:31:30 +00:00			`# Add the installation directory to the system-wide paths`
			`echo $INSTALL_DESTINATION \| tee -a /etc/paths.d/dotnet`

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-09 21:26:37 +00:00			`exit 0`