All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Chad Hanson <chanson@TrustedCS.com>,
	Daniel J Walsh <dwalsh@redhat.com>,
	Joshua Brindle <jbrindle@tresys.com>,
	SELinux <SELinux@tycho.nsa.gov>
Subject: Re: [PATCH] Add seuser and user_extra to package format
Date: Tue, 07 Feb 2006 09:59:59 -0500	[thread overview]
Message-ID: <43E8B5EF.1030101@cornell.edu> (raw)
In-Reply-To: <1139322866.2872.44.camel@moss-spartans.epoch.ncsc.mil>


>> I will resync my nodecon patch tomorrow - let me know if anything's 
>> wrong with it, otherwise will submit as is (ordering pending in a later 
>> patch).
>>     
>
> I still wasn't clear on the disposition of the pylist patch.
>   
I think the typemap code would be sufficiently different in diff. 
languages, that we can (and will have to) write a completely new .i file 
for another language. I doubt the current typemap code is language 
portable (I don't know how adding things to output vector will translate 
to other languages). It seems to me that the portable portion of the 
code is generated by swig, and any typemaps we add on top will be mostly 
language specific.

Dan, maybe you can comment on this. I added a patch that translates 
out-bound C list (type**, int) to an actual PyList, which is garbage 
collected, and you can have a for-in loop range over it without an 
index, and you don't need get_*_by_idx. There are probably other 
advantages that I don't know about. Would this be useful to a python 
developer? What about an in-bound PyList (for set_roles)?  Do iterate() 
function pointers work currently? If not, maybe better python 
integration can help make them work?

> For the nodecon patch, I wasn't sure if we were sufficiently confident
> in the ABI/API stability to include it for FC5 or if it should wait on
> FC6 devel.  It would likely help to have feedback from potential users
> of the nodecon API.
>   
Ok... I would like to hear any recommendations on byte order/byte array 
handling.

--
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-07 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 22:39 [PATCH] Add seuser and user_extra to package format Joshua Brindle
2006-02-07  3:04 ` Ivan Gyurdiev
2006-02-07  3:10   ` Joshua Brindle
2006-02-07 14:34   ` Stephen Smalley
2006-02-07 14:59     ` Ivan Gyurdiev [this message]
2006-02-07 15:20       ` Daniel J Walsh
2006-02-07 17:52     ` Joshua Brindle
2006-02-07 18:15       ` Daniel J Walsh
2006-02-07 20:05       ` Ivan Gyurdiev
2006-02-07 21:23         ` Joshua Brindle

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=43E8B5EF.1030101@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=chanson@TrustedCS.com \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.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.