public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] libargp 20110921-1 (ping)
Date: Tue, 27 Sep 2011 14:06:00 -0000	[thread overview]
Message-ID: <fsk387lldvfpf7giuv224omu36gdvmab1q@4ax.com> (raw)
In-Reply-To: <n5on77hs0gl82obpjb05l3o753gsc2ueq9@4ax.com>

> I'd like to package and maintain libargp for Cygwin.  argp is a C interface for
> processing command line arguments.
> 
> The libargp source files are taken from gnulib.  gnulib is a well-known program
> available in major Linux distros (e.g. http://packages.debian.org/sid/gnulib),
> but I'm not aware of any distros that separately package just argp from it.  So
> I'm not sure if libargp needs to be voted on or not for inclusion in Cygwin.
> 
> Documentation:     http://www.gnu.org/s/hello/manual/libc/Argp.html
> Source home page:  http://www.gnu.org/s/gnulib/MODULES.html
> License:           LGPL

Package maintainers, please consider voting in favor of libargp for Cygwin.

I don't know of any rule that says I can't vote for my own package, so I'm
voting +1 for libargp.  I want it specifically to use with nosleep [1].  I
could have just baked the argp source files statically into nosleep, but they
would have made up the bulk of the code, which seemed silly.  It seems better
to make libargp available for shared use.

Thanks,
Andrew.

[1] http://cygwin.com/ml/cygwin-apps/2011-09/msg00079.html

  reply	other threads:[~2011-09-27 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23  1:28 [ITP] libargp 20110921-1 Andrew Schulman
2011-09-27 14:06 ` Andrew Schulman [this message]
2011-09-27 14:24   ` [ITP] libargp 20110921-1 (ping) Christopher Faylor
2011-09-27 14:45     ` Andrew Schulman
2011-09-27 17:17       ` David Rothenberger
2011-09-27 18:30         ` Andrew Schulman
2011-09-27 18:31         ` Christopher Faylor
2011-09-27 15:03     ` Reini Urban
2011-09-27 15:14       ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fsk387lldvfpf7giuv224omu36gdvmab1q@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).