From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux List <SELinux@tycho.nsa.gov>,
Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [SEMANAGE(lib/tool)] Remove add_local/set_local
Date: Fri, 13 Jan 2006 15:24:09 -0700 [thread overview]
Message-ID: <43C82889.7020901@cornell.edu> (raw)
In-Reply-To: <1137160220.3445.116.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Mon, 2006-01-09 at 13:14 -0700, Ivan Gyurdiev wrote:
>
>> Hi, this patch removes add_local and set_local functions from the dbase
>> API, since they duplicate other functionality.
>>
>
> Merged as of libsemanage 1.5.12 and policycoreutils 1.29.6.
> I then later had to move the semanage tool diffs over to the new
> seobject.py introduced by Dan in a later policycoreutils.
>
Steven, will you be increasing the major number with the next official
release? Some of the changes made are suspect API changes (size_t
conversion in sepol/semanage, commit numbers in semanage, compare
behavior in sepol/semanage), and this one is a clear change... What
about sepol?
If the number will be increased, I'll change some other not-so-smart
APIs, like port_get_proto_str, and fcontext_get_proto_str, which should
take an integer, and return a string, instead of taking a port or
context. We could also deprecate some things in sepol, or add more
handles here and there.
--
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.
next prev parent reply other threads:[~2006-01-13 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:14 [SEMANAGE(lib/tool)] Remove add_local/set_local Ivan Gyurdiev
2006-01-13 13:50 ` Stephen Smalley
2006-01-13 22:24 ` Ivan Gyurdiev [this message]
2006-01-18 16:27 ` 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=43C82889.7020901@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--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.