From: Glauber de Oliveira Costa <glommer@br.ibm.com>
To: Steve G <linux_4ever@yahoo.com>
Cc: Selinux@tycho.nsa.gov
Subject: Re: [PATCH] add version option to newrole
Date: Wed, 8 Feb 2006 11:32:53 -0200 [thread overview]
Message-ID: <200602081132.53649.glommer@br.ibm.com> (raw)
In-Reply-To: <20060208130613.7417.qmail@web51501.mail.yahoo.com>
Steve, thanks a lot for your comments,
Em Quarta 08 Fevereiro 2006 11:06, Steve G escreveu:
> >@@ -10,7 +10,7 @@
> > *
> > * USAGE:
> > *
> >- * newrole [ -r role ] [ -t type ] [ -l level ] [ -- args ]
> >+ * newrole [ -r role ] [ -t type ] [ -l level ] [ -v ] [ -- args ]
> > *
> > * BUILD OPTIONS:
> > *
>
> Args doesn't sound descriptive to me.
What do you suggest instead? -v is what is commonly associated with version
options in most programs.
> >diff -upNr policycoreutils-1.29.18/newrole/version.h
> >policycoreutils-1.29.18.mine/newrole/version.h
> >--- policycoreutils-1.29.18/newrole/version.h 1969-12-31
> > 21:00:00.000000000 -0300
> >+++ policycoreutils-1.29.18.mine/newrole/version.h 2006-02-07
> >16:15:47.000000000
> >-0200
> >@@ -0,0 +1,4 @@
> >+
> >+#ifndef VERSION
> >+#define VERSION "1.29.18"
> >+#endif
>
> Version is traditionally kept in config.h or the makefiles. The version
> isn't unique to newrole. there are other apps in the same package that have
> the same version number. If we do one, we should do them all and put the
> definition in a central location like the toplevel Makefile.
See my mail. I stated that if the option is of interest, I may implement it in
these other packages. This first patch was just an initial attempt. A
version.h (though auto-generated as Stephen suggested) is still my choice.
But I'll take a look about putting it in the Makefile. My main concern is
being able to compile it from newrole (or whatever) directory, not from the
top level one.
> -Steve
Thanks again,
glauber.
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
--
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.
next prev parent reply other threads:[~2006-02-08 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 11:34 [PATCH] add version option to newrole 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-08 16:45 [PATCH] Add " 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
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=200602081132.53649.glommer@br.ibm.com \
--to=glommer@br.ibm.com \
--cc=Selinux@tycho.nsa.gov \
--cc=linux_4ever@yahoo.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 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.