Update mcollective.init

In sh the argument -e throws an error.
Snapshot from solaris 10 manual
     -e file                 True if file exists. (Not  available
                             in sh.)
Update pkginfo

Correct the NAME from mcollective- to mcollective
+ delete the description in NAME
Update build

With Release param package name from mcollective doesn't confirm the Naming.
You can check the naming with chkcat

https://github.com/dex4er/pkgutil/blob/master/chkcat
Merge pull request #168 from Reamer/master

Update mcollective.init
(maint) Remove i18n bits from packaging

i18n was removed before the 2.4.0 release, but some remnants are left in
packaging. This commit removes the dependency from the client gem and also
removes them from the gem_excludes list.
Merge pull request #171 from haus/cleanup_i18n_pieces

(maint) Remove i18n bits from packaging
(MCO-192) Implement back-off at the connector level

This commit adds higher level for exponential backoff to the
connectors.  The STOMP gem's support for exponential backoff only
handles tcp-level failures.  Here we allow for protocol-level
issues such as incorrect credentials causing a disconnection.

In order to do that we add a new execption class, BackoffSuggestion,
and two specific exception classes derived from it that allow the
code that raises the error to make a suggestion about how long the
handler should wait before proceeding.  These two classes are
MessageNotReceived for when the connector is unable to receive a
message, and UnexpectedMessageType for when a message isn't of the
kind you were expecting.  For STOMP these map to connector.receive
== nil and msg.command != 'MESSAGE' respectively.

As part of this change to the flow we refactor the tests heavily to allow for
pluginconfig to be resolved in the initializer of the connector, as we use the
existing stomp gem keepalive settings for our own connector-level
`exponential_back_off` method.
Merge pull request #172 from richardc/MCO-192

(MCO-192) Implement back-off at the connector level
(MCOP-17) Add dist macro to Release field

When building the same plugin for multiple platforms at once, it is important
for the NVR of those packages to be unique for certain deployment platforms
like satellite. Previously the release did not include the dist macro, which
is the easiest way to ensure a unique NVR across platforms. This commit adds
the dist macro to the Release field. This means that instead of having an NVR
like mco-plugin-1.2.1-1 everywhere, now the NVR will be
mco-plugin-1.2.1-1.fc19, mco-plugin-1.2.1-1.el5, etc. The leading ? in the
macro means that if undefined, nothing will be printed, but it won't be an
error.
Merge pull request #173 from haus/ticket/master/mcop_17_add_dist_tag

(MCOP-17) Add dist macro to Release field