Downloads:

1,088

Downloads of v 0.9.6:

323

Last Update:

01 Feb 2015

Package Maintainer(s):

Software Author(s):

  • karanikolas

Tags:

fuel scm fossil tool

Fuel SCM (Portable)

This is not the latest version of Fuel SCM (Portable) available.

0.9.6 | Updated: 01 Feb 2015

Downloads:

1,088

Downloads of v 0.9.6:

323

Maintainer(s):

Software Author(s):

  • karanikolas

Fuel SCM (Portable) 0.9.6

This is not the latest version of Fuel SCM (Portable) available.

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test


Validation Testing Unknown


Verification Testing Passed

Details

To install Fuel SCM (Portable), run the following command from the command line or from PowerShell:

>

To upgrade Fuel SCM (Portable), run the following command from the command line or from PowerShell:

>

To uninstall Fuel SCM (Portable), 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 fuelscm.portable -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 fuelscm.portable -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 fuelscm.portable installed
  win_chocolatey:
    name: fuelscm.portable
    state: present
    version: 0.9.6
    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 'fuelscm.portable' do
  action    :install
  version  '0.9.6'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: fuelscm.portable,
    Version: 0.9.6,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller fuelscm.portable
{
   Name     = 'fuelscm.portable'
   Ensure   = 'Present'
   Version  = '0.9.6'
   Source   = 'STEP 3 URL'
}

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


package { 'fuelscm.portable':
  provider => 'chocolatey',
  ensure   => '0.9.6',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install fuelscm.portable version="0.9.6" 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 is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator purity on 02 Feb 2015.

Description

Fuel is cross-platform GUI front-end to the excellent Fossil SCM tool written in Qt. Fuel runs on Windows, OSX as well as various flavors of Unix including Linux and FreeBSD.


tools\chocolateyInstall.ps1
try {
  $package = 'fuelscm'
  $PackageVersion = "0.9.6"
  $url = "http://fuelscm.org/files/releases/Fuel-0.9.6-win32.zip"
  $destination = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" 

  Install-ChocolateyZipPackage $package -url $url -unzipLocation $destination
} catch {
  Write-ChocolateyFailure $package "$($_.Exception.Message)"
  throw
}
tools\fossil.exe.ignore
 

Log in or click on link to see number of positives.

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
Fuel SCM (Portable) 0.9.6 323 Sunday, February 1, 2015 Approved

Fuel V0.9.6 (2012-05-13)

  • Feature: Support for fossil stashes
  • Feature: Support for dragging and dropping files out of Fuel
  • Feature: Allow for opening workspaces via the checkout file or a workspace folder
  • Feature: Display the actual file icons
  • Feature: Windows: Shift-Right-Click invokes the Explorer file context menu
  • Feature: Allow starting Fuel into an existing fossil workspace via the command line (Thanks Chris)
  • Feature: Portable mode. When starting Fuel with the "--portable" option all settings
    will be stored in a Fuel.ini file. If a settings file already exists, Fuel will start
    into portable mode automatically. (Thanks Chris)
  • Improvement: Always show unknown files when starting a new repository
  • Bug Fix: Avoid specifying filenames explicitly when all modified files are selected.
    This addresses an issue preventing commits after a merge
  • Bug Fix: Fixed issue where a complete repository would be committed even when
    the user has a specific set of files marked for commit
  • Misc: Minor GUI bug fixes and usability enhancements

This package has no dependencies.

Discussion for the Fuel SCM (Portable) Package

Ground Rules:

  • This discussion is only about Fuel SCM (Portable) and the Fuel SCM (Portable) 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 Fuel SCM (Portable), 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