Notices: This section not yet converted to new layout. Download stats are rolling back out.

This is not the latest version of classified-ads (Install) available.

classified-ads (Install)

0.09

Package test results are passing.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator doc on 1/3/2016.

Classified ads is a distributed internet messaging system that requires no server-side support of any kind. It allows users to post public and private messages, display basic details about themselves and do searches over data posted online.

In practice it allows you to do about same kind of things that you can do with web-forums and e-mail but here you don't need to deal with any kind of "service provider", here users provide service to each others. This also makes the software reliable as there is no "service that would go down" or cease to exist, leaving users with no correspondence.

To install classified-ads (Install), run the following command from the command line or from PowerShell:

C:\> choco install classified-ads --version 0.09

To upgrade classified-ads (Install), run the following command from the command line or from PowerShell:

C:\> choco upgrade classified-ads --version 0.09

Files

Hide
  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop'; # stop on all errors
    $packageName = 'classified-ads' 
    $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    
    $url = 'https://github.com/operatornormal/classified-ads/raw/859e7c54842485347330814fb235ba971ffecf42/Classified-ads-Win32.exe' # download url
    
    $packageArgs = @{
      packageName   = $packageName
      unzipLocation = $toolsDir
      fileType      = 'exe' 
      url           = $url
    
      #MSI
      silentArgs    = "/S" 
      validExitCodes= @(0, 3010, 1641)
      registryUninstallerKey = 'classified-ads' #ensure this is the value in the registry
      checksum      = 'cf6850c4ec711835bc56616e53a237c668572da2'
      checksumType  = 'sha1' #default is md5, can also be sha1
    }
    
    Install-ChocolateyPackage @packageArgs
    
  • tools\chocolateyuninstall.ps1 Show
    $package = 'classified-ads'
    $installFolder = 'Classified-ads'
    
    try
    {
      $installPath = (Join-Path "${Env:\ProgramFiles(x86)}" $installFolder),
        (Join-Path $Env:ProgramFiles $installFolder) |
        ? { Test-Path $_ } |
        Select -First 1
    
      $uninstall = Join-Path $installPath 'uninstall.exe'
    
      #uses NSIS installer - http://nsis.sourceforge.net/Docs/Chapter3.html
      $uninstallParams = @{
        PackageName = $package;
        FileType = 'exe';
        SilentArgs = '/S';
        File = $uninstall;
      }
    
      Uninstall-ChocolateyPackage @uninstallParams
    
      $binLocation = (Join-Path $installPath 'bin') -replace '\\', '\\'
    
      $userPaths = [Environment]::GetEnvironmentVariable('Path', 'User') -split ';' |
        ? { ($_ -notmatch $binLocation) -and (![String]::IsNullOrEmpty($_)) } |
        Select-Object -Unique
    
      [Environment]::SetEnvironmentVariable('Path', ($userPaths -join ';'), 'User')
    }
    catch
    {
      Write-ChocolateyFailure $package "$($_.Exception.Message)"
      throw
    }
  • tools\ReadMe.md Show
    ## Summary
    How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages
    
    If you are submitting packages to the community feed (https://chocolatey.org)
    always try to ensure you have read, understood and adhere to the create
    packages wiki link above.
    
    ## Automatic Packages?
    Consider making this package an automatic package, for the best 
    maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages
    
    ## Shim Generation
    Any executables you include in the package or download (but don't call 
    install against using the built-in functions) will be automatically shimmed.
    
    This means those executables will automatically be included on the path.
    Shim generation runs whether the package is self-contained or uses automation 
    scripts. 
    
    By default, these are considered console applications. 
    
    If the application is a GUI, you should create an empty file next to the exe 
    named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.
    See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui
    
    If you want to ignore the executable, create an empty file next to the exe 
    named 'name.exe.ignore' e.g. 'bob.exe' would need a file named 
    'bob.exe.ignore'. 
    See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects
    
    ## Self-Contained? 
    If you have a self-contained package, you can remove the automation scripts 
    entirely and just include the executables, they will automatically get shimmed, 
    which puts them on the path. Ensure you have the legal right to distribute 
    the application though. See https://github.com/chocolatey/choco/wiki/Legal. 
    
    You should read up on the Shim Generation section to familiarize yourself 
    on what to do with GUI applications and/or ignoring shims.
    
    ## Automation Scripts
    You have a powerful use of Chocolatey, as you are using PowerShell. So you
    can do just about anything you need. Choco has some very handy built-in 
    functions that you can use, these are sometimes called the helpers.
    
    ### Built-In Functions
    https://github.com/chocolatey/choco/wiki/HelpersReference
    
    A note about a couple:
    * Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder. 
    * Install-BinFile - used for non-exe files - executables are automatically shimmed...
    * Uninstall-BinFile - used for non-exe files - executables are automatically shimmed
    
    ### Getting package specific information
    Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument
    
    ### Need to mount an ISO?
    https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package
    
    
    ### Environment Variables
    Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):
    
     * TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
     * ChocolateyInstall = Top level folder where Chocolatey is installed
     * chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
     * chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
     * chocolateyPackageFolder = The top level location of the package folder
    
    #### Advanced Environment Variables
    The following are more advanced settings:
    
     * chocolateyPackageParameters = (0.9.8.22+)
     * CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
        - Otherwise take a dependency on the specific version you need. 
     * chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
        - Automatically handled in built in Choco functions. 
     * OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
     * OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
     * OS_NAME = The reported name of the OS. (0.9.9+)
     * IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)
     
    #### Experimental Environment Variables
    The following are experimental or use not recommended:
    
     * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
     * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
        - it's based on git describe
     * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
     * chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
     * chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)
    
    

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Maintainer(s)

Software Author(s)

  • Antti Järvinen

Copyright

Copyright (C) Antti Järvinen and others, 2013

Tags

Release Notes

Bugfix release 10-Oct-2015

Version History

Version Downloads Last updated Status
classified-ads (Install) 0.09 89 Sunday, October 11, 2015 approved
classified-ads (Install) 0.07 81 Monday, September 7, 2015 approved

Discussion for the classified-ads (Install) Package

Ground rules:

  • This discussion is only about classified-ads (Install) and the classified-ads (Install) 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 classified-ads (Install), 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