Skip to content

Releases: MatejKafka/Pog

Pog v0.7.2

09 Apr 14:23
Compare
Choose a tag to compare

Full Changelog: v0.7.1...v0.7.2

  • Fix URL escaping issue, remote packages with spaces in names should now work.

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run Pog/setup.cmd.

Local repository support

To use a local package repository for development, use the following script to import the Pog PowerShell module:

$env:POG_LOCAL_REPOSITORY_PATH = "..."
Import-Module Pog

Pog v0.7.1

08 Apr 21:23
Compare
Choose a tag to compare

Full Changelog: v0.7.0...v0.7.1

  • Remote repository is now the default. Not that it's stable yet, but whatever. :)
  • Added Get-UrlHash cmdlet available to package generators to simplify generating manifests.

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run Pog/setup.cmd.

Local repository support

To use a local package repository for development, use the following script to import the Pog PowerShell module:

$env:POG_LOCAL_REPOSITORY_PATH = "..."
Import-Module Pog

Pog v0.7.0

02 Apr 21:39
Compare
Choose a tag to compare

Full Changelog: v0.6.0...v0.7.0

  • Experimental support for remote repositories (see below)
  • All commonly used external cmdlets ported to C#
  • Add scaffolding for unit tests
  • Add basic CI

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run Pog/setup.cmd.

Remote repository support

To experimentally use a remote repository, use the following script to import the Pog PowerShell module:

$env:POG_REMOTE_REPOSITORY_URL = "https://matejkafka.github.io/PogPackages/"
Import-Module Pog

Pog v0.6.0

11 Sep 04:38
Compare
Choose a tag to compare

Full Changelog: v0.5.0...v0.6.0

  • Lot of cmdlets ported to C#, resulting in better performance, argument consistency and validation.
  • Pog stub improvements – support for environment variable interpolation, better job setup, bug fixes.
  • Packages can now declare that they need VS Redistributable and Pog provides it during setup.

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run Pog/setup.cmd.

Pog v0.5.0

30 Aug 08:01
Compare
Choose a tag to compare

Full Changelog: v0.4.0...v0.5.0

  • Added experimental Disable-Pog and Uninstall-Pog cmdlets.
  • Better PowerShell 5 support.
  • Lot of internal plumbing improvements, especially around file download and internal cmdlet invocation.
  • Until a better setup script is implemented, 7zip and OpenedFilesView are shipped in the release archive.

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run Pog/setup.cmd.

Pog v0.4.0

11 Aug 14:12
Compare
Choose a tag to compare

Second public pre-release.

  • Pog should now work correctly with PowerShell 5, PowerShell Core is no longer necessary.
  • Until a better setup script is implemented, 7zip and OpenedFilesView are shipped in the release archive.

Installation

  1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
  2. Download and unpack the archive to your preferred directory for portable applications.
  3. Run Pog/setup.cmd.

Basic usage

After Pog is installed, open a PowerShell window and use pog <package-name> to download your first package. To view the documentation, use the internal man cmdlet (e.g. man Get-PogPackage).

Pog v0.3.0

16 Jun 01:31
Compare
Choose a tag to compare

First public pre-release. Until a better setup script is implemented, 7zip and OpenedFilesView are shipped in the release archive.

Installation

  1. Ensure you have PowerShell 7.0 installed (support for lower versions, especially PowerShell 5, is in progress).
  2. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that too in a future release).
  3. Download and unpack the archive to your preferred directory for portable applications.
  4. Run Pog/setup.cmd.