From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, Daniel J Walsh <dwalsh@redhat.com>
Subject: [SEMANAGE] Swig update
Date: Sat, 24 Dec 2005 16:09:25 -0500 [thread overview]
Message-ID: <43ADB905.8090801@cornell.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
This updates the swig interfaces (adding ports and active booleans), and
reorders the headers so they make sense. I haven't checked if the port
typemap things are correct - just uncommented.
I remember last time I updated swig interfaces I wrote to the wrap file
directly, instead of the interface (didn't realize it was autogenerated)
- maybe make clean should get rid of it to avoid confusion.
[-- Attachment #2: libsemanage9.swig_update.diff --]
[-- Type: text/x-patch, Size: 2247 bytes --]
diff -Naurp --exclude-from excludes old/libsemanage/src/semanageswig.i new/libsemanage/src/semanageswig.i
--- old/libsemanage/src/semanageswig.i 2005-12-24 16:03:22.000000000 -0500
+++ new/libsemanage/src/semanageswig.i 2005-12-24 15:41:15.000000000 -0500
@@ -147,7 +147,6 @@
/* the wrapper will setup this parameter for passing... the resulting python functions
will not take the semanage_port_t *** parameter */
-/*
%typemap(in, numinputs=0) semanage_port_t ***(semanage_port_t **temp) {
$1 = &temp;
}
@@ -171,27 +170,25 @@
%typemap(in, numinputs=0) semanage_port_key_t **(semanage_port_key_t *temp) {
$1 = &temp;
}
-*/
/* pull in the headers */
-%include "../include/semanage/boolean_record.h"
%include "../include/semanage/debug.h"
-%include "../include/semanage/interfaces_policy.h"
-%include "../include/semanage/booleans_local.h"
-%include "../include/semanage/handle.h"
-%include "../include/semanage/modules.h"
-%include "../include/semanage/semanage.h"
+%include "../include/semanage/handle.h"
+%include "../include/semanage/modules.h"
+%include "../include/semanage/context_record.h"
+%include "../include/semanage/boolean_record.h"
+%include "../include/semanage/booleans_policy.h"
+%include "../include/semanage/booleans_local.h"
+%include "../include/semanage/booleans_active.h"
+%include "../include/semanage/iface_record.h"
+%include "../include/semanage/interfaces_local.h"
+%include "../include/semanage/interfaces_policy.h"
%include "../include/semanage/user_record.h"
-%include "../include/semanage/booleans_policy.h"
-%include "../include/semanage/iface_record.h"
-%include "../include/semanage/seuser_record.h"
%include "../include/semanage/users_local.h"
-%include "../include/semanage/context_record.h"
-%include "../include/semanage/interfaces_local.h"
-%include "../include/semanage/seusers.h"
%include "../include/semanage/users_policy.h"
-/*
%include "../include/semanage/port_record.h"
%include "../include/semanage/ports_local.h"
%include "../include/semanage/ports_policy.h"
-*/
+%include "../include/semanage/seuser_record.h"
+%include "../include/semanage/seusers.h"
+%include "../include/semanage/semanage.h"
next reply other threads:[~2005-12-24 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 21:09 Ivan Gyurdiev [this message]
2006-01-04 15:02 ` [SEMANAGE] Swig update Stephen Smalley
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=43ADB905.8090801@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.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.