google_talkplugin

Manages the google-talkplugin package

Joshua Hoblitt

jhoblitt

7,618 downloads

7,618 latest version

4.6 quality score

Version information

  • 0.1.0 (latest)
released Jun 16th 2015
This version is compatible with:
  • RedHat
    ,
    CentOS
    ,
    Scientific
    ,
    Fedora

Start using this module

Documentation

jhoblitt/google_talkplugin — version 0.1.0 Jun 16th 2015

Puppet google_talkplugin Module

Build Status

Table of Contents

  1. Overview
  2. Description
  3. Usage
  4. Limitations
  5. Versioning
  6. Support
  7. Contributing
  8. See Also

Overview

Manages the google-talkplugin package

Usage

include ::google_talkplugin
#defaults
class { 'google_talkplugin':
    manage_repo => true,
}

Limitations

Tested Platforms

  • el7.x
  • Fedora 21
  • Fedora 22

Requires a newer version of glibc than is present on el6.x:

Error: Package: google-talkplugin-5.41.0.0-1.x86_64 (google-talkplugin)
           Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit)
Error: Package: google-talkplugin-5.41.0.0-1.x86_64 (google-talkplugin)
           Requires: libc.so.6(GLIBC_2.14)(64bit)

Versioning

This module is versioned according to the Semantic Versioning 2.0.0 specification.

Support

Please log tickets and issues at github

Contributing

  1. Fork it on github
  2. Make a local clone of your fork
  3. Create a topic branch. Eg, feature/mousetrap
  4. Make/commit changes
    • Commit messages should be in imperative tense
    • Check that linter warnings or errors are not introduced - bundle exec rake lint
    • Check that Rspec-puppet unit tests are not broken and coverage is added for new features - bundle exec rake spec
    • Documentation of API/features is updated as appropriate in the README
    • If present, beaker acceptance tests should be run and potentially updated - bundle exec rake beaker
  5. When the feature is complete, rebase / squash the branch history as necessary to remove "fix typo", "oops", "whitespace" and other trivial commits
  6. Push the topic branch to github
  7. Open a Pull Request (PR) from the topic branch onto parent repo's master branch

See Also