Re: [ SEPOL ] Move more things to newer debug system

[Ivan Gyurdiev <ivg2@cornell.edu>]

Ivan Gyurdiev wrote:

>
>>> Next, what to do we do with all those printf calls that remain, and 
>>> the ones
>>> that are now DEBUG calls.... if they are in fact error-reporting 
>>> statements,
>>> then I understand you want them written in an error buffer. Where does
>>> the buffer come from, given the current API?
>>>   
>>
>>
>> What particular interfaces are an issue here?
>
> All of them? For example, the policydb.c code just changed to use 
> DEBUG...
> policydb_read()
> policydb_write()
> everything else...


Well... I guess those would be in the static library. In fact, the 
shared library doesn't provide a whole lot of functionality right now:

  global: sepol_genbools*; sepol_set_policydb_from_file; 
sepol_check_context; sepol_genusers; sepol_debug; sepol_set_delusers;

So, if you deprecate the shared sepol_gen*, you're left 
with...sepol_check_context (which makes use of sepol_context_to_sid, and 
sepol_ctx_*)... and also sepol_set_policydb_from_file (which I think 
should also be deprecated, along with the global policydb).

Why are we making this a static library again?



--
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.