All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glauber de Oliveira Costa <glommer@br.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Selinux@tycho.nsa.gov, Steve G <linux_4ever@yahoo.com>
Subject: Re: [PATCH] Add version option to newrole
Date: Fri, 10 Feb 2006 11:51:17 -0200	[thread overview]
Message-ID: <200602101151.17945.glommer@br.ibm.com> (raw)
In-Reply-To: <1139515974.3452.41.camel@moss-spartans.epoch.ncsc.mil>

Em Quinta 09 Fevereiro 2006 18:12, Stephen Smalley escreveu:
> On Thu, 2006-02-09 at 15:09 -0500, Stephen Smalley wrote:
> > At present, your patch causes newrole to display the version number of
> > the entire collection (policycoreutils), not an individual version tied
> > to the newrole program itself.  Thus, I think it should display the
> > PACKAGE string as well (already defined) as part of the message, e.g.:
> > 	printf("%s:  %s version %s\n", argv[0], PACKAGE, VERSION);
> > yielding output like:
> > 	newrole:  policycoreutils version 1.29.20

argv[0] will display the complete path of the command being called. I think 
this is not what we want. 

> > Otherwise, the patch seems sane and suitable for the other utilities as
> > well.  A few of the utilities appear to have their own version string at
> > present, but I think you can just drop that as no one is maintaining
> > that - only the top-level VERSION for the entire collection is
> > meaningful.
>
> Also, using -v is ambiguous, as it often means to run a program under a
> verbose mode (extra output), and several utilities are using -v in that
> way, so use -V and/or --version instead.

Sure this is confusing. A lot of programs use -v for version (see GNU 
Binutils), some don't use a shortopt at all (see GNU coreutils), and some use 
the suggested -V (see GNU zip). I'll cope with your suggestion and use -V 

I'll send a new version of newrole's implementation together with the manpage 
patch soon, and patches for the other programs as soon as I can too.

glauber.
 

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2006-02-10 13:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 16:45 [PATCH] Add version option to newrole Glauber de Oliveira Costa
2006-02-08 16:54 ` Stephen Smalley
2006-02-08 17:10 ` Steve G
2006-02-08 17:16   ` Glauber de Oliveira Costa
2006-02-09 20:09 ` Stephen Smalley
2006-02-09 20:12   ` Stephen Smalley
2006-02-10 13:51     ` Glauber de Oliveira Costa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-08 11:34 [PATCH] add " Glauber de Oliveira Costa
2006-02-08 12:43 ` Stephen Smalley
2006-02-08 13:25   ` Glauber de Oliveira Costa
2006-02-08 13:06 ` Steve G
2006-02-08 13:32   ` Glauber de Oliveira Costa

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=200602101151.17945.glommer@br.ibm.com \
    --to=glommer@br.ibm.com \
    --cc=Selinux@tycho.nsa.gov \
    --cc=linux_4ever@yahoo.com \
    --cc=sds@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.