[Apparmor-dev] AppArmor Development

[Jacob I. Torrey]

I have written a number of lexers & parsers, perhaps that would be a
better place to start, then branch out from there. Where can I look at
the current parser?

JT

John Johansen wrote:
> Jacob I Torrey wrote:
>   
>> I think that would be a great start for me, unless someone has any
>> objections, are there any docs on coding style?
>>
>>     
> Not an objection, but a warning this isn't as easy as it sounds at
> first, at least not if you are removing redundant rules, and detecting
> conflicting rules.
>
> The other caveat is the parsing library isn't in a finished state yet,
> so each app has roled its own parsing (which is bad).
>
> Before diving into this I would like to get a discussion on two and
> three way merging.  I have a lot of notes on doing this, I will dig them
> up and post them.
>
> As for coding style, the project has been moving to towards lkml style
> C, but most of the code is a real mismash of styles currently.  As for
> language, things are currently mostly C, C++ and perl though if you are
> working on a new tool, I don't have objections to picking a new language.
>
>   
>> If I get you correctly, I need to write a program that'll take the name
>> of two programs and merge their profiles, and perhaps an export profile
>> function (unless this is done).
>>
>>     
> Yes an export profile function is needed, in general what is needed is a
> complete parsing library, that can be shared by all the user side tools.
>
> But if you want I have no objections to rolling your own (more likely
> just stealing current code) and getting started on a project and then
> dropping in the parsing library when it is done.
> _______________________________________________
> Apparmor-dev mailing list
> Apparmor-dev at forge.novell.com
> http://forge.novell.com/mailman/listinfo/apparmor-dev
>
>