Re: First crack at argparse parser for semanage.

[mark]

David Quigley wrote:
>  I posted this yesterday but sent it from the wrong account so its
probably in moderation.
>  Attached is my first crack at the argparse version of semanage. Right 
now it just
parses the command line and spits out the dictionary raw.
Please mess around with the command line and make sure that it behaves
how you would expect. Some of the names in the dictionary are a bit
weird and I'm having trouble getting sensible semantics for fcontext -e
but it should be parsing the command lines properly. Also not all of the
help text is in place yet. If you want to add some help text either send
it to me in an email or send me a patch and I'll apply it to my repo. I
still need to commit the latest changes to my github account but once I
do you should be able to get the same file from my semanage-argparse
repo on github. After we're sure that the parsing works as we'd like and
the help messages are sensible to people I'll work on gluing this
frontend back onto the seobject class that semanage uses to do that
actual policy store manipulations. Someone pointed out that I have some
spelling mistakes in there. I will make sure to address them in the next
version once I add more help text.
>  
Well, if you're screwing with semanage's syntax...
can't the bizarre
syntax of wildcards be changed to something *normal*? Y'know, like make
semanage fcontext -a -t httpd_sys_content_t /web\*
?
And why doesn't semanage have a was to set -t u?

       mark

First crack at argparse parser for semanage.

[David Quigley]

On 04/18/2013 10:12, m.roth(a)5-cent.us wrote:
>  David Quigley wrote:
> > I posted this yesterday but sent it from the wrong account so its
>  probably in moderation.
> >
> > Attached is my first crack at the argparse version of semanage. 
> > Right
>  now it just parses the command line and spits out the dictionary raw.
>  Please mess around with the command line and make sure that it 
>  behaves
>  how you would expect. Some of the names in the dictionary are a bit
>  weird and I'm having trouble getting sensible semantics for fcontext 
>  -e
>  but it should be parsing the command lines properly. Also not all of 
>  the
>  help text is in place yet. If you want to add some help text either 
>  send
>  it to me in an email or send me a patch and I'll apply it to my repo. 
>  I
>  still need to commit the latest changes to my github account but once 
>  I
>  do you should be able to get the same file from my semanage-argparse
>  repo on github. After we're sure that the parsing works as we'd like 
>  and
>  the help messages are sensible to people I'll work on gluing this
>  frontend back onto the seobject class that semanage uses to do that
>  actual policy store manipulations. Someone pointed out that I have 
>  some
>  spelling mistakes in there. I will make sure to address them in the 
>  next
>  version once I add more help text.
> >
>  Well, if you're screwing with semanage's syntax... can't the bizarre
>  syntax of wildcards be changed to something *normal*? Y'know, like 
>  make
>  semanage fcontext -a -t httpd_sys_content_t /web\*
>  ?
>  And why doesn't semanage have a was to set -t u?
>
>         mark
>
>
>
>  --
>  selinux mailing list
>  selinux(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/selinux 



I'm not sure I understand your last question. Also I'm trying not to 
mess with the syntax so we don't obsolete all the documentation out 
there.

Dave

First crack at argparse parser for semanage.

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/18/2013 10:12 AM, m.roth(a)5-cent.us wrote:
>  David Quigley wrote:
> > I posted this yesterday but sent it from the wrong account so its
>  probably in moderation.
> > 
> > Attached is my first crack at the argparse version of semanage. Right
>  now it just parses the command line and spits out the dictionary raw. 
>  Please mess around with the command line and make sure that it behaves how
>  you would expect. Some of the names in the dictionary are a bit weird and
>  I'm having trouble getting sensible semantics for fcontext -e but it should
>  be parsing the command lines properly. Also not all of the help text is in
>  place yet. If you want to add some help text either send it to me in an
>  email or send me a patch and I'll apply it to my repo. I still need to
>  commit the latest changes to my github account but once I do you should be
>  able to get the same file from my semanage-argparse repo on github. After
>  we're sure that the parsing works as we'd like and the help messages are
>  sensible to people I'll work on gluing this frontend back onto the seobject
>  class that semanage uses to do that actual policy store manipulations.
>  Someone pointed out that I have some spelling mistakes in there. I will
>  make sure to address them in the next version once I add more help text.
> > 
>  Well, if you're screwing with semanage's syntax... can't the bizarre syntax
>  of wildcards be changed to something *normal*? Y'know, like make semanage
>  fcontext -a -t httpd_sys_content_t /web\* ? And why doesn't semanage have a
>  was to set -t u?
>  
>  mark
>   
Sadly the syntax comes from using Regular expressions for labeling rather then
glob.  Not likely to change.

>  
>  -- selinux mailing list selinux(a)lists.fedoraproject.org 
>  https://admin.fedoraproject.org/mailman/listinfo/selinux
>  
>   
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlFwQI4ACgkQrlYvE4MpobMQcwCfdJtDBvSOVjTcILmtytdbW83U
> LUkAnRlYrwFvoTW7fH7Aa6SxhkN1c/+u
> =fZoI
> -----END PGP SIGNATURE-----