Re: RFS: google-gflags
On Fri, 2009-04-10 at 08:52 -0700, Ehren Kret wrote: > On Sat, Apr 11, 2009 at 01:29:23AM +1000, Matthew Palmer wrote: > The distinctive feature of this library that I'm aware of is that it > allows command line flags to be defined in any file in which they're > needed and uses the linker to aggregate the flags into a single list for > parse-time. > > Here's what their docs say about this: > Google's commandline flags library differs from other libraries, such > as getopt(), in that flag definitions can be scattered around the source > code, and not just listed in one place such as main(). In practice, > this means that a single source-code file will define and use flags > that are meaningful to that file. Any application that links in that > file will get the flags, and the google commandline flags library will > automatically handle that flag appropriately. Hardly distinctive, I wrote that in libgetopt++ in (checks changelog) 2002. -Rob signature.asc Description: This is a digitally signed message part
Re: RFS: google-gflags
On Sat, Apr 11, 2009 at 01:29:23AM +1000, Matthew Palmer wrote: > On Fri, Apr 10, 2009 at 08:06:54AM -0700, Ehren Kret wrote: > > It builds these binary packages: > > libgoogle-gflags-dev - a commandline flags processing library > > libgoogle-gflags0 - a commandline flags processing library > > Considering the plethora of other libraries to process command line flags, I > think you'll need to "sell" this thing a little more. What does it do that > the competition just doesn't do? Is it needed for another package? And so > on. > > - Matt > The distinctive feature of this library that I'm aware of is that it allows command line flags to be defined in any file in which they're needed and uses the linker to aggregate the flags into a single list for parse-time. Here's what their docs say about this: Google's commandline flags library differs from other libraries, such as getopt(), in that flag definitions can be scattered around the source code, and not just listed in one place such as main(). In practice, this means that a single source-code file will define and use flags that are meaningful to that file. Any application that links in that file will get the flags, and the google commandline flags library will automatically handle that flag appropriately. signature.asc Description: Digital signature
Re: RFS: google-gflags
On Fri, Apr 10, 2009 at 08:06:54AM -0700, Ehren Kret wrote: > It builds these binary packages: > libgoogle-gflags-dev - a commandline flags processing library > libgoogle-gflags0 - a commandline flags processing library Considering the plethora of other libraries to process command line flags, I think you'll need to "sell" this thing a little more. What does it do that the competition just doesn't do? Is it needed for another package? And so on. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: google-gflags
Dear mentors, I am looking for a sponsor for my package "google-gflags". * Package name: google-gflags Version : 1.0-1 Upstream Author : Google Inc. * URL : http://code.google.com/p/google-gflags/ * License : New BSD License Section : libs It builds these binary packages: libgoogle-gflags-dev - a commandline flags processing library libgoogle-gflags0 - a commandline flags processing library The package appears to be lintian clean. The upload would fix these bugs: 523411 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/google-gflags - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/google-gflags/google-gflags_1.0-1.dsc I would be glad for feedback and/or if someone uploaded this package for me. Thank you, -- Ehren Kret signature.asc Description: Digital signature
