Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "sblim-wbemcli"

   Package name    : sblim-wbemcli
   Version         : 1.6.2-4
   Upstream Author : Tyrel Datwyler <tyr...@us.ibm.com>
   URL             : 
http://sourceforge.net/apps/mediawiki/sblim/index.php?title=Wbemcli
   License         : Eclipse Public License -v 1.0
   Programming Lang: C++
   Section         : misc

It builds those binary packages:

      sblim-wbemcli - WBEM Command Line Interface
  sblim-wbemcli-dbg - debugging symbols for sblim-wbemcli

To access further information about this package, please visit the following 
URL:
  http://mentors.debian.net/package/sblim-wbemcli

Alternatively, one can download the package with dget using this command:
  dget -x 
http://mentors.debian.net/debian/pool/main/s/sblim-wbemcli/sblim-wbemcli_1.6.2-4.dsc

As an introduction, let me quote its long description from the homepage
of the sblim SourceForge project (http://sblim.wiki.sourceforge.net):

 The WBEM Command Line Interface is a standalone, convenient systems
 management utility for CIMOM access. Invocation and output syntax are
 problem-oriented and well suited for interactively inclusion in Shell
 and Perl scripts. It is especially suited for administrators writing
 their own management scripts or for WBEM developers that want to test
 their providers.

WBEM (Web-Based Enterprise Management) is a successor of SNMP and the
basis of SMI-S (Storage Management Initiative), a standard interface to
storage devices.  WBEM itself has a much wider scope, thus more
ambitious projects like OpenPegasus exist, but the single wbemcli module
of the sblim project is enough to monitor disk and RAID states in SMI-S
compatible storage products for example.  This is also my actual use-
case and reason for packaging it: using an OS-component in our
monitoring system is much easier than carrying along custom binaries.

wbemcli is also part of the Ubuntu WBEM stack; see for example
https://wiki.ubuntu.com/WBEMStackSpec for evaluation of the
alternatives.

Comments, questions and sponsors are much appreciated.  Actually, I'm
rather uncertain about the header format of the patch gcc4.7-fixes,
which could use two Origin fields due to CVS' inability to export
patches touching multiple files, but DEP-3 does not seem to allow such
construction...

Also, the admin, net and utils sections all seem more appropriate than
the current misc.  Which one should I choose?
-- 
Thanks,
Feri.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to