admin/PowerShell-PowerShell
1
0
Fork 0
mirror of https://github.com/PowerShell/PowerShell synced 2026-06-08 12:12:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix incorrect function references in releasing.md

Browse Source 
This documentation is meant to describe Start-PSPackage, not Start-PSBuild.
This commit is contained in:
Andrew Schwartzmeyer
2016-09-06 15:53:09 -07:00
committed by GitHub
parent 7a89b33f8b
commit 8911e72477
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/maintainers/releasing.md
+3 -3
View File
@@ -48,7 +48,7 @@ It **requires** that `Start-PSBuild -CrossGen` has been run.
Linux / macOS
------------
The `Start-PSBuild` function delegates to `New-UnixPackage`.
The `Start-PSPackage` function delegates to `New-UnixPackage`.
This function will automatically deduce the correct version from the most recent annotated tag (using `git describe`).
At this time, each package must be made on the corresponding platform.
@@ -56,7 +56,7 @@ The packages each have the .NET Core runtime-identifier appended to their filena
This is necessary to differentiate the Ubuntu 14.04 and 16.04 packages,
which must be separate due to having different dependencies.
The `Start-PSBuild` function relies on the [Effing Package Management][fpm] project,
The `Start-PSPackage` function relies on the [Effing Package Management][fpm] project,
which makes building packages for any (non-Windows) platform a breeze.
Similarly, the PowerShell man-page is generated from the Markdown-like file
[`assets/powershell.1.ronn`][man] using [Ronn][].
@@ -123,7 +123,7 @@ package will instead be created.
Windows
-------
The `Start-PSBuild` function delegates to `New-MSIPackage` which creates a Windows Installer Package of PowerShell.
The `Start-PSPackage` function delegates to `New-MSIPackage` which creates a Windows Installer Package of PowerShell.
The packages *must* be published in release mode, so use `Start-PSBuild -CrossGen -Configuration Release`.
It uses the Windows Installer XML Toolset (WiX) to generate a `PowerShell_<version>.msi`,
which installs a self-contained copy of the current version (commit) of PowerShell.