edbbc64b03
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.
13 lines
318 B
Bash
Executable file
13 lines
318 B
Bash
Executable file
#!/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 -R 755 $INSTALL_DESTINATION/shared
|
|
|
|
exit 0
|