Downloads:

4,169

Downloads of v 2016.4.1:

592

Last Update:

11/24/2016

Package Maintainer(s):

Software Author(s):

  • FlightGear Team

Tags:

flightgear flight simulator game admin foss cross-platform

FlightGear

2016.4.1 | Updated: 11/24/2016

Downloads:

4,169

Downloads of v 2016.4.1:

592

Maintainer(s):

Software Author(s):

  • FlightGear Team

FlightGear 2016.4.1

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Dependencies require reboot, therefore exemption required

To install FlightGear, run the following command from the command line or from PowerShell:

>

To upgrade FlightGear, run the following command from the command line or from PowerShell:

>

To uninstall FlightGear, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade flightgear -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade flightgear -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure flightgear installed
  win_chocolatey:
    name: flightgear
    state: present
    version: 2016.4.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'flightgear' do
  action    :install
  version  '2016.4.1'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: flightgear,
    Version: 2016.4.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller flightgear
{
   Name     = 'flightgear'
   Ensure   = 'Present'
   Version  = '2016.4.1'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'flightgear':
  provider => 'chocolatey',
  ensure   => '2016.4.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install flightgear version="2016.4.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 11/25/2016.

Description

FlightGear is an open-source flight simulator.
It supports a variety of popular platforms (Windows, Mac, Linux, etc.) and is developed by skilled volunteers from around the world.
Source code for the entire project is available and licensed under the GNU General Public License.

The goal of the FlightGear project is to create a sophisticated and open flight simulator framework for use in research or academic environments,
pilot training, as an industry engineering tool, for DIY-ers to pursue their favorite interesting flight simulation idea,
and last but certainly not least as a fun, realistic, and challenging desktop flight simulator.

Notes

  • If kb2919355 hasn't been installed previously,
    and you are running on Windows 8.1 or Windows Server 2012 R2.
    Then it must be installed and a reboot must occur before trying to install FlightGear.
    Otherwise installation may fail.

tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$version = '2016.4.1'
$softwareName = "FlightGear v$version"

$packageArgs = @{
  packageName = 'flightgear'
  fileType    = 'exe'
  url         = 'http://ftp.igh.cnrs.fr/pub/flightgear/ftp/Windows/FlightGear-2016.4.1.exe'

  softwareName = $softwareName

  checksum     = '8B1851999233047E3DA451AFB2739C5024E914E92011B3F5F37E42CDB5ED1F64'
  checksumType = ''

  silentArgs   = '/VERYSILENT'
  validExitCodes = @(0)
}

$key = UninstallRegistryKey -SoftwareName $softwareName

if ($key) {
  Write-Host "FlightGear $version is already installed. Skipping download and installation."
} else {
  Install-ChocolateyPackage @packageArgs
}
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop';

$packageName = 'flightgear'

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName 'FlightGear*'

if ($key.Count -eq 1) {
  $key | % {
    $packageArgs = @{
      packageName = $packageName
      fileType    = 'exe'
      silentArgs  = '/VERYSILENT'
      validExitCodes= @(0)
      file          = "$($_.UninstallString)"
    }

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
FlightGear 3.4.0 424 Tuesday, February 17, 2015 Approved
FlightGear 3.2.0 598 Sunday, October 19, 2014 Unknown
FlightGear 3.0.0.20141014 306 Tuesday, October 14, 2014 Unknown
FlightGear 3.0.0 396 Tuesday, February 18, 2014 Unknown
FlightGear 2.12.1 352 Wednesday, November 27, 2013 Unknown

Discussion for the FlightGear Package

Ground Rules:

  • This discussion is only about FlightGear and the FlightGear package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or FlightGear, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus